Bump php-wasm and php-cgi-wasm to 0.0.9-alpha-21

still need to patch for https://github.com/seanmorris/php-wasm/issues/62 I believe

and https://github.com/seanmorris/php-wasm/issues/67

Since we hit a bug in vrzno on streams with HTTP method configured, I opened an MR which just bumps sqlite https://git.drupalcode.org/project/drupal_cms/-/merge_requests/149

tried alpha23, failure: https://git.drupalcode.org/issue/drupal_cms-3483001/-/jobs/3154364#L82

⎯⎯⎯⎯ Unhandled Rejection ⎯⎯⎯⎯⎯
TypeError: Headers.append: "" is an invalid header name.
 ❯ node:internal/deps/undici/undici:12618:11

I think it's this HTTP/2 bug in undici, maybe a node 18 issue? https://github.com/nodejs/undici/pull/2332 I'll have to run it locally on my node 22 to see

quirk in vrnzo, seanmorris found out and is working on a fix

alpha24 is out and needs a try

Okay we're close. It looks like setting env for CGI isn't working in the latest alpha

The env value is respected. It's just that the form submission isn't working the same as it used to for some reason. The default value is sqlite but form validation has gone sideways.

To unblock D11 support, I'll merge !149 now, then work on the other component can continue.

Back to the ol' drawing board!

We found out the "bug": php-wasm added pdo_postgres support but it is compiled statically, not as a shared library like the other pdo extensions. So Drupal thinks Postgres is available and that's why the interactive installer test broke. We just need to workaround this in the trial installer.

Debugged MR !153 with some guidance from @mglaman and discovered that our logic around submitting the database settings form was flawed - we need to assertively send it our default value when there is more than one choice available. Previously this worked by accident because SQLite was the only game in town, but the updated runtime also supports PostgreSQL, which meant that we were using SQLite but validating against Postgres' settings because of how the database form works.

This is now fixed.

What a slog this was to get done, but we got it done. And VRZNO is part of this update, so we get HTTP support now too - amazing!

Automatically closed - issue fixed for 2 weeks with no activity.