Beanstalkd bury jobs
Nobody has claimed this yet.
- Dominant language
- PHP
- Stars
- 1.1k
- Forks
- 285
- Avg merge
- 5d 3h
- Merged PRs (30d)
- 2
Description
Hi, I'm asking once more for this.
As you can see #62 was closed without a real answer, because buring jobs is part of Beanstalkd core and it's a common practice that all Beanstalkd client implements (like Pheanstalk).
I've clearly stated why bury jobs can be useful and that behavior can be configurable (delete failed jobs or otherwise bury failed jobs).
Did you maybe accept a PR for this?
Contributor guide
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
Review this request alongside issue #62 and the repository's Beanstalkd support. Establish how failed jobs should expose configurable deletion versus burying, then define tests that distinguish both behaviors before implementation.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- php
- Domain
- backend, distributed-systems
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100