channable / channable/opsqueue
Feature: Client receives asynchronous `ChunkReservationExpired` not actionable from library
Open
enhancement
- Dominant language
- Rust
- Stars
- 96
- Forks
- 2
- Avg merge
- 1h 2m
- Merged PRs (30d)
- 2
Description
https://github.com/channable/opsqueue/blob/bd0a42e7f45ccd2750071e3dd3cd9bd4dda4fd25/opsqueue/src/consumer/client.rs#L293-L295
I would expect a local cancellation token that we can await to be informed we should stop processing the `Chunk`.
Contributor guide
No contributing guide indexed for this repository
Research direction
Start in opsqueue/src/consumer/client.rs at lines 293-295 and trace how ChunkReservationExpired is delivered to the client. Determine how an awaitable local cancellation token should signal that processing of the Chunk must stop, then verify the expiration path informs consumers as requested.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- distributed-systems
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100