Solution #1

Revert to Node 18

Solution #2

I'm̀ still looking for one

The post Compiling node-canvas with Node 20 fails with ‘v8::AccessorSignature’ has not been declared appeared first on Techy Things.

Solution #1

Go on Linux, it doesnt have this problem.

Solution #2

Use canvas npm instead of node-canvas. This one works better.

Solution #3

Install GTK

The post node-canvas on Windows fails with Warning: Missing input files: C:\GTK\bin\libpangowin32-1.0-0.dll etc appeared first on Techy Things.

frank@angel:~$ sudo mount -a
The disk contains an unclean file system (0, 0).
Metadata kept in Windows cache, refused to mount.
Falling back to read-only mount because the NTFS partition is in an
unsafe state. Please resume and shutdown Windows fully (no hibernation
or fast restarting.)
Could not mount read-write, trying read-only
mount: (hint) your fstab has been modified, but systemd still uses
the old version; use 'systemctl daemon-reload' to reload.

Solution

frank@angel:~$ sudo ntfsfix /dev/sdb2
Mounting volume... The disk contains an unclean file system (0, 0).
Metadata kept in Windows cache, refused to mount.
FAILED
Attempting to correct errors...
Processing $MFT and $MFTMirr...
Reading $MFT... OK
Reading $MFTMirr... OK
Comparing $MFTMirr to $MFT... OK
Processing of $MFT and $MFTMirr completed successfully.
Setting required flags on partition... OK
Going to empty the journal ($LogFile)... OK
Checking the alternate boot sector... OK
NTFS volume version is 3.1.
NTFS partition /dev/sdb2 was processed successfully.

The post The disk contains an unclean file system (0, 0). Could not mount read-write, trying read-only appeared first on Techy Things.

However some options need to be adjusted in some of the database entries:

• <prefix>usermeta :
  • wp_capabilites => <prefix>capabilities
  • wp_user_level => <prefix>user_level
• <prefix>_option :
  • wp_user_roles => <prefix>user_roles\

Reference

https://blog.juansorroche.com/wordpress-vous-n-avez-pas-les-droits-suffisants-pour-acceder-a-cette-page

The post Vous n’avez pas les droits suffisants pour accéder à cette page appeared first on Techy Things.

This can happen when upgrading i18next from version "19.9.2" to  "22.5.1".

The wait option that got removed was :

export interface ReactOptions {
  /**
   * Set to true if you like to wait for loaded in every translated hoc
   * @default false
   */
  wait?: boolean;

And what is useSuspense used for ? Let's check the documentation

Wow very useful, thank you !

Actually Suspense is a React feature. It was first added for server-side lazy rendering but is also available on client-side frontends. It's used for lazy loading components. If you don't know what it is you are probably not using it. Then the default is fine since this parameter might not even affect your project.

As a side note in plugin options declaration that have default values, it's best not to declare option's parameters to the default value for two reasons:

1. It's more readable if the default options are not included. Your config then lists only non-default values and you can grasp more easily how the config differs from other peoples project. In general default values are chosen carefully and should be changed only when having a good reason to.
2. It's more maintainable. When the option is removed by the plugin/module maintainer and replaced or renamed, your config adapts automatically. This case is an example. If the coder had not written the useless `wait: false` which is anyway the default value, it would not have broke during upgrade.

The post TS2322: Type '{ wait: false; }' is not assignable to type 'ReactOptions'. appeared first on Techy Things.

Compilation error: 'lv_obj_get_style_opa_recursive' was not declared in this scope; did you mean 'lv_obj_get_style_img_recolor'?

Solution

LVGL was version 8.3.8
Need to upgrade to at least 8.3.10

The post LVGL_Music.cpp:323:20: error: 'lv_obj_get_style_opa_recursive' was not declared in this scope; did you mean 'lv_obj_get_style_img_recolor'? appeared first on Techy Things.

Fatal error: Uncaught PDOException: SQLSTATE[HY000] [2002] No connection could be made because the target machine actively refused it. in U:\Webpages\yipp.ca\app\src\db.inc.php:28 Stack trace: #0 U:\Webpages\yipp.ca\app\src\db.inc.php(28): PDO->__construct('mysql:host=37.2...', 'yipp', 'hPKcxOvXnwvPX5R...') #1 U:\Webpages\yipp.ca\app\src\db.inc.php(38): getDB() #2 U:\Webpages\yipp.ca\app\src\routes.php(27): require_once('U:\\Webpages\\yip...') #3 U:\Webpages\yipp.ca\app\public_html\index.php(28): require('U:\\Webpages\\yip...') #4 {main} thrown in U:\Webpages\yipp.ca\app\src\db.inc.php on line 28

Check the causes & solutions below.

Reason #1

mariaDB or mySQL is not listening on the public IP but only on localhost.

Put the public IP of the server in /etc/mysql/mariadb.conf.d/50-server.cnf at the line "bind-address".
For example if your server IP is 123.123.123.123:

(...)
# Instead of skip-networking the default is now to listen only on
# localhost which is more compatible and is not less secure.
bind-address            = 123.123.123.13

Some people like putting 0.0.0.0 there which will require less editing and downtime if your IP changes or you migrate to another server/IP.

Reason #2

You are connecting to the wrong server IP. Your server IP might have changed. Or if using the hostname, make sure the hostname resolves to the right IP. Try pinging it to see the IP it resolves to.

Reason #3

The SQL user you are trying to reach doesn't have permission to login from your client IP.
Usually mySQL or mariaDB will block any connection from a remote IP for a user unless the user@yourip is whitelisted.
This whitelisting is done directly in the users table in SQL.

Reason #4

iptables or other firewall are actively blocking the connection. Disable temporarily the firewall to test if this is the case. Note that there could be multiple reasons at once. Before trying this, make sure reasons 1 to 3 are not happening.

The post The four causes for "No connection could be made because the target machine actively refused it" in mariaDB or mySQL appeared first on Techy Things.

Generating development JavaScript bundle failed

You must provide the URL of lib/mappings.wasm by calling SourceMapConsumer.initialize({ 'lib/mappings.wasm': ... })
before using SourceMapConsumer

File: .cache\app.js

Solution

Add

--no-experimental-fetch

like such

 

You can try to add it in package.json but this may fail sometimes if your command expect optional arguments. The full proof way is to add it to .env in the directory as package.json to add it as an environment variable like above.

The post You must provide the URL of lib/mappings.wasm by calling SourceMapConsumer.initialize ERROR #98123 WEBPACK appeared first on Techy Things.

Current versions used, along with node v18.

  "@types/react-dom": "^18.2.7",
  "@types/react": "18.0.2",

This can occur when switching from node 16 or lower to node 18 or more.

This is similar to this unanswered question https://github.com/FormidableLabs/victory/discussions/2632

Solution #1

Solution #2

npm install --save-dev @types/react@latest
npm install --save-dev @types/react-dom@latest

or

yarn add --dev @types/react@latest
yarn add --dev @types/react-dom@latest

The post TS2786: 'VictoryAxis' cannot be used as a JSX component appeared first on Techy Things.

The post Uncaught TypeError: axios.create is not a function appeared first on Techy Things.