RFC: Consider providing an easy way to "drain" the queue for testing purposes
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 25/100
Research direction
Start by inspecting the batcher implementation and its specs to determine how queued work is currently flushed; the issue provides no file or test path. Done means specs can drain queued batches without shutting down the batcher, with integration behavior covered by tests.
Written by the indexing model from the issue text.
Description
It'd be nice to drain the batcher in specs without shutting it down so that we don't have to resort to things like this on specs in case we want to do some integration testing 💭
Maybe it is possible but I don't know how to do it so please LMK in case there is
cc @divoxx
- Dominant language
- Ruby
- Stars
- 2
- Forks
- 1
- 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.
Similar issues
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
hanami/hanami-cli#449 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
resque/resque-scheduler#826 ·
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100