letsencrypt / letsencrypt/boulder
bad-key-revoker: be more robust to failing one task
Open
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 5.8k
- Forks
- 649
- Avg merge
- 3d 23h
- Merged PRs (30d)
- 24
Description
In #6520, it was possible for bad-key-revoker to get stuck on all work because there was a bug that affected only a single task. We should change bad-key-revoker so that non-transient errors in a single task don't hold up work on all tasks.
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
Start by reviewing the bad-key-revoker implementation and issue #6520 to understand how one task failure currently affects the queue. Done means a non-transient error in one task is handled without preventing other tasks from being processed.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- backend, security
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100