KillingSpark / KillingSpark/zstd-rs
FrameCompressor should expose write errors
Open
Beginner friendly
good first issue
- Dominant language
- Rust
- Stars
- 449
- Forks
- 66
- PR merge metrics
- No merged PRs in 30d
Description
`FrameCompressor` currently unwraps any errors from the writer during compression. These errors should be bubbled up to the caller instead, so that they can decide how to handle them.
Contributor guide
No contributing guide indexed for this repository
Research direction
Start by locating FrameCompressor and trace how writer errors are handled during compression. Verify that those errors reach the caller rather than being unwrapped, and add or update coverage for the error path if the surrounding code provides tests.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- backend
- Issue type
- Bug
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Quiet
- Clarity
- Clearly specified
- Newbie friendliness
- 68/100