rivet-dev / rivet-dev/dynamic-apps
Conformance: Stream/fs/http implementation gaps blocking upstream tests
Open
Nobody has claimed this yet.
enhancement
- Dominant language
- TypeScript
- Stars
- 1k
- Forks
- 51
- Avg merge
- 6m
- Merged PRs (30d)
- 13
Description
Various upstream Node.js tests fail due to implementation gaps in bridged modules:
- fs: VFS doesn't support watch/watchFile, symlinks, permissions bits, BigInt stat fields, createReadStream/createWriteStream edge cases
- stream: Internal stream state behavior differs from Node.js (backpressure, error propagation, pipeline edge cases)
- http: Server request/response lifecycle edge cases, keep-alive, transfer encoding
Tracked via conformance test exclusions (category: implementation-gap).
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 upstream Node.js conformance tests and the conformance test exclusions marked category: implementation-gap. Group the failures across fs, stream, and http, then address the implementation gaps until the relevant upstream tests pass without those exclusions.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- node.js, typescript
- Domain
- backend, testing-qa
- Issue type
- Bug
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100