rivet-dev / rivet-dev/dynamic-apps
@agentos-software/wget: wasm build bug (duplicate getsockname/getpeername vs patched sysroot), blocks publish
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 1k
- Forks
- 51
- Avg merge
- 6m
- Merged PRs (30d)
- 13
Description
@agentos-software/wget is unpublished — its wasm build fails, so registry/publish-software.sh skips it:
case "$n" in wget|duckdb|make|build-essential) ... wget - build bug (duplicate getsockname/getpeername vs patched sysroot)
Problem: duplicate getsockname/getpeername symbols conflict with the patched WASI sysroot when building wget for wasm32-wasip1 (versions: [] on npm).
Impact: agent-os packages/shell depended on @agentos-software/wget; it was dropped from packages/shell to unblock agent-os CI. Re-add once the wasm build lands.
Done when: the symbol conflict is resolved, wget builds to wasm32-wasip1, publish-software.sh no longer excludes it, the package publishes, and it's restored to agent-os packages/shell.
Contributor guide
No contributing guide indexed for this repository
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
Start with the wasm32-wasip1 build failure and the duplicate getsockname/getpeername symbols conflicting with the patched WASI sysroot. Review registry/publish-software.sh and the wget exclusion, then verify the package can build and publish. Done means the conflict is resolved, wget is restored to agent-os packages/shell, and the package has a published version.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- shell, wasm
- Domain
- build-system, release
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 50/100