Failed queue items should not be dropped from the queue
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 25/100
Research direction
No files or tests are identified in the issue. Start by tracing how failed queue items are handled, then determine the intended retry or retention behavior and add coverage showing that failed items are not silently dropped, with an optional policy if that remains the requirement.
Written by the indexing model from the issue text.
Description
Or at very least it should be optional. Some queues we have these days are supposed to be robust and guarantee that every incoming item is processed.
- Dominant language
- C#
- Stars
- 15
- Forks
- 8
- PR merge metrics
- No merged PRs in 30d
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.
More from ppy/osu-queue-processor
-
Difficulty 3/5 1-2 days Newbie friendliness 35/100
ppy/osu-queue-processor#13 · 1 comment ·
All issues in ppy/osu-queue-processor
Similar issues
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
nightscout/nocturne#1425 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
RayWangQvQ/BiliBiliToolPro#1137 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 70/100