WebAssembly / WebAssembly/WASI
Inconsistency with wasi:http@0.2.0 snapshots
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 5.8k
- Forks
- 333
- Avg merge
- 2d 13h
- Merged PRs (30d)
- 3
Description
It looks like the wasi:http@0.2.0 package in this repository only provides the proxy world, but the wasi:http@0.2.0 package over in https://github.com/WebAssembly/wasi-http/blob/main/wit/proxy.wit#L5 also provides the imports world.
This can confuse some tooling (and humans) because both (the same?) packages are versioned as 0.2.0 but don't supply the same worlds.
It'd be great if we could sync them now and then implement a way to ensure they stay in sync with future updates.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Compare preview2/http/proxy.wit in the WASI repository with wit/proxy.wit in the wasi-http repository, focusing on the worlds exposed by the wasi:http@0.2.0 package. Determine how the definitions should be synchronized and how future divergence could be detected. Done means the 0.2.0 snapshots agree and a maintainable synchronization check or process is established.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- wasm
- Domain
- api, operating-systems
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100