max-mapper / max-mapper/byte-stream
needs time threshold too
Open
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 22
- Forks
- 5
- PR merge metrics
- No merged PRs in 30d
Description
say the buffer is 16mb and you are writing data slowly, it would be nice if byte-stream had both a byte limit and also a time limit, so if you are aren't writing very fast byte-stream could emit non-full batches based on some timeout parameter
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
No files or tests are named. Start by tracing byte-stream's existing cumulative byte-size batching behavior, then determine how a timeout parameter should interact with partial batches and slow writes. Done means the timeout behavior is implemented and covered for non-full batches.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- backend
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100