rivet-dev / rivet-dev/dynamic-apps
WasmVM: statvfs/fstatvfs not available in WASI
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 1k
- Forks
- 51
- Avg merge
- 6m
- Merged PRs (30d)
- 13
Description
Summary
statvfs() and fstatvfs() are not part of WASI Preview 1 — there is no filesystem statistics interface available. Programs calling these functions will fail.
Affected os-test cases
basic/sys_statvfs/statvfsbasic/sys_statvfs/fstatvfs
Category
wasi-gap — WASI Preview 1 does not expose filesystem statistics (block size, free blocks, etc.).
Notes
These were previously linked to issue #34 (stat metadata) which is a different issue. statvfs requires host-level filesystem information that the WASI sandbox does not provide.
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 affected os-test cases, basic/sys_statvfs/statvfs and basic/sys_statvfs/fstatvfs, and inspect how the test harness reports their WASI Preview 1 failures. The issue names no implementation entry point or supported replacement, so completion requires an agreed approach for handling the missing filesystem-statistics interface and passing behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- wasm
- Domain
- operating-systems
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100