Conversation
PR preview (
|
kilyanni
force-pushed
the
rustfs
branch
2 times, most recently
from
July 21, 2026 15:47
2f0ac44 to
150ded7
Compare
kilyanni
force-pushed
the
rustfs
branch
4 times, most recently
from
July 21, 2026 17:47
e4741d6 to
d985821
Compare
Build report18 eval/upload failures · 1 built · 525 rebuilt vs base · 18 new eval failures · 515/584 outputs identical
❌
|
PR preview (
|
kilyanni
force-pushed
the
rustfs
branch
2 times, most recently
from
July 23, 2026 19:53
7f02a51 to
cf643fd
Compare
Cross-compile rustfs (github.com/rustfs/rustfs, a MinIO-class erasure-coded S3 store, ~1070-crate lock incl. datafusion) to wasm32-wasmer-wasi and run its CLI under wasmer. Built with -p rustfs, no-default-features (drops the deeply-unix ftps/webdav servers), and a fast release profile override: the stock opt3+thin-LTO+cgu1 whole-program link on a ~190MB wasm froze for 1h+. Source mods (patches applied post-vendor so .rs edits don't re-vendor): - rustfs-manifest.patch: switch the whole rustls stack off native aws-lc-rs onto pure-Rust ring (AWS SDK, google-cloud, reqwest, vaultrs, lapin, mysql, nats, mqtt, otlp, libunftp, jsonwebtoken); drop mimalloc; stub tokio signal. - rustfs-code.patch: wasi arms for the storage core (rustfs is a filesystem: os get_info/same_disk/device-ids, O_DIRECT, statvfs, MetadataExt, device major/minor), mimalloc FFI gating, ring provider call sites, a 5GiB usize overflow on wasm32. Dependency crate-patches (stock upstream, applied by the vendor-patch hook): tokio (net/fs guard + I/O-driver ENOTSUP), getrandom, netif, rustls-native-certs, symlink, crc-fast, clocksource, async-rs, tonic, tokio-postgres, deadpool-postgres, google-cloud-auth, rustfs-kafka, and the two runtime fixes below. Runtime blockers found by the smoke tests and fixed at the source quirk: - wasite: whoami read the OS username via the WASI preview-2 wasi:cli environment interface, which a preview1 host cannot import; read std::env. - parking_lot_core: its atomic wasm parker was gated behind the cargo `nightly` feature, so wasix (which has atomics) fell to a panic stub; select wasm_atomic.rs on wasi. - tokio I/O driver: wasmer's poll_oneoff returns ENOTSUP (not EINVAL) for an empty subscription set, which tokio's wasi arm did not catch; accept it too. wasmer root cause tracked in WASIX-TODO.md. Tests: two mkWasixRun smoke tests (rustfs --version / --help) run the wasm under wasmer and pass cleanly (correct output, exit 0, no panics). server/info are not yet tested (server needs mio's unimplemented wasip1 Waker). Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
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.
No description provided.