Add missing functions required to succesfully connect with MySQL DB

[jeroenpf]

Motivation for the change, related issues

When trying to connect to a MySQL database (in my case version 8.4.0) several errors regarding unreachable code were triggered, making the site unusable.

I've added the required functions one by one until there were no more errors and I was able to successfully run a site with MySQL.

The errors seem to be related to how MySQL handles authentication specifically.

Implementation details

I did not yet run a full build as I am not sure if there are any additional steps needed to do that. I would appreciate some help with this.

Testing Instructions (or ideally a Blueprint)

• Run a MySQL database with Docker (use latest)
• Remove SQLite integration plugin from WordPress Playground site and change wp-config.php to point to 127.0.0.1 and provide valid db credentials.
• Observe that trying to use the MySQL db with a Playground site causes errors.
• Build a new wasm binary and use it (and the accompanying js file) with the Playground site.
• Observe that now the site works with MySQL.

[jeroenpf]

@brandonpayton Do you have a chance to look at this?

[adamziel]

I did not yet run a full build as I am not sure if there are any additional steps needed to do that. I would appreciate some help with this.

The Dockerfile changes look great and there aren't any other changes required besides rebasing and building. See #1716 which did the same thing for another set of C functions.

[adamziel]

Also, does Electron support JSPI? I was thinking about shipping a set of JSPI binaries for runtimes that support it, it would solve this entire class of Asyncify problems.

[fluiddot]

Also, does Electron support JSPI? I was thinking about shipping a set of JSPI binaries for runtimes that support it, it would solve this entire class of Asyncify problems.

I haven't specific documentation but I think it currently doesn't. However, Electron uses Chromium so if there's a way to enable that feature maybe we could give it a try.

[adamziel]

@fluiddot actually, how are you running Playground? Is it via the chromium JavaScript engine? If so, the chrome://flags/#enable-experimental-webassembly-jspi flag would do the trick. Or are you also shipping Node.js? If yes, can you ship Node v22? See the compat matrix: #1339

[fluiddot]

@fluiddot actually, how are you running Playground? Is it via the chromium JavaScript engine? If so, the chrome://flags/#enable-experimental-webassembly-jspi flag would do the trick. Or are you also shipping Node.js? If yes, can you ship Node v22? See the compat matrix: #1339

@adamziel Ah, interesting. Playground is actually running via Node.js (version v20.17.0). I double-checked and Chromium is mainly used for rendering the frontend, and the JS engine is used for the view logic. As far as I know, Node.js is pre-bundled in Electron, so if we want to use a newer version we'd need to rebuild it. This will likely need to patch Electron due to potential incompatibilities. I'm not sure about the complexity fo this, but I presume it could be relatively high because the Node.js is a bit coupled to other dependencies in Electron like Chromium (example: electron/electron#43428).

[brandonpayton]

The Dockerfile changes look great and there aren't any other changes required besides rebasing and building. See #1716 which did the same thing for another set of C functions.

@jeroenpf once this is rebased and the php-wasm binaries are rebuilt, this should be good to go.

You may already be familiar with building php-wasm, but just in case, you can do so with the following commands:

• npm run rebuild:php:node
• npm run rebuild:php:web

[jeroenpf]

@fluiddot It looks like support for Node 22 will be added somewhere around November if we go by this chart.

[fluiddot]

@fluiddot It looks like support for Node 22 will be added somewhere around November if we go by this chart.

Great! In that case, we could explore JSPI in a couple of months. I looked for a a potential alpha/beta build in Electron but looks like there's none with Node 22 yet.

[jeroenpf]

@adamziel - I've compiled new wasm binaries so we should be good to go :-)

[brandonpayton]

Note: I'm trying to test this briefly before merging and releasing updated NPM packages, but my environment seems to be dealing with some kind of caching issue that is preventing Playground from loading.

Looking into it.

[adamziel]

@brandonpayton The same issue happened on my end today! Just randomly between two page refreshes. I thought it's weird and specific to my setup, but apparently not

[brandonpayton]

@adamziel, thanks for mentioning! I'm going to merge this because it is testing well in another browser, and trunk is equally broken in Chrome anyway. The routing (#1731) branch loads fine, so it must be something to do with caching. I'll keep looking at that after merging this because something unexpected is going on...

[brandonpayton]

This looks fine, passes the tests, and tests well locally. Thank you!

[brandonpayton]

@jeroenpf, we just released NPM package updates that include your changes.

[jeroenpf]

@brandonpayton thanks! 🙏