ci(wasip2): document and test wasm32-wasip2 support (Postgres + MySQL)#4309
Open
ricochet wants to merge 1 commit into
Open
ci(wasip2): document and test wasm32-wasip2 support (Postgres + MySQL)#4309ricochet wants to merge 1 commit into
ricochet wants to merge 1 commit into
Conversation
SQLx already runs on wasm32-wasip2 with no library changes: the standard
`runtime-tokio` feature works there because Tokio's `net` driver builds on
WASI via mio. Pooling, LISTEN/NOTIFY, timeouts, and rustls TLS all work.
Building for the target requires `--cfg tokio_unstable` and a current-thread
runtime (WASI has no threads in wasip2 target).
This documents and exercises that support:
- README: add a WebAssembly (`wasm32-wasip2`) section covering the
`runtime-tokio` setup, the two target requirements, what works, and the
remaining limitations (hostname lookup needs `--allow-ip-name-lookup`,
native-tls is unavailable, MySQL caching_sha2 over plaintext needs
`mysql-rsa`).
- examples/wasip2/{postgres,mysql}: runnable pool examples that do a real
round-trip — create a table, insert rows in a transaction with bind
parameters, read them back ranked, and aggregate. A shared
`.cargo/config.toml` sets `--cfg tokio_unstable` so a plain
`cargo build --target wasm32-wasip2` works.
- CI: a `wasip2` job builds both examples and runs them under Wasmtime
against Postgres and MySQL service containers, asserting the query
output to catch wasm-specific decode regressions.
Signed-off-by: Bailey Hayes <bailey@cosmonic.com>
Contributor
Author
|
CI on main is failing. Created a PR to fix: #4311 |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
SQLx already runs on wasm32-wasip2 with no library changes: the standard
runtime-tokiofeature works there because Tokio'snetdriver builds on WASI via mio. Pooling, LISTEN/NOTIFY, timeouts, and rustls TLS all work. Building for the target requires--cfg tokio_unstableand a current-thread runtime (WASI has no threads in wasip2 target).This exercises that support:
wasm32-wasip2) section covering theruntime-tokiosetup, the two target requirements, what works, and the remaining limitations (hostname lookup needs--allow-ip-name-lookup, native-tls is unavailable, MySQL caching_sha2 over plaintext needsmysql-rsa)..cargo/config.tomlsets--cfg tokio_unstableso a plaincargo build --target wasm32-wasip2works.wasip2job builds both examples and runs them under Wasmtime against Postgres and MySQL service containers, asserting the query output to catch wasm-specific decode regressions.