letsencrypt / letsencrypt/boulder
publisher: share backoff state between goroutines
Open
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 5.8k
- Forks
- 649
- Avg merge
- 3d 23h
- Merged PRs (30d)
- 24
Description
Right now when a log serves an error, the goroutine submitting to that log will retry and backoff. We should track which CT logs have thrown errors recently and have some per-process, per-CT log backoff state.
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
No files or tests are named. Start by locating the publisher's CT log submission and retry/backoff entry points, then trace how goroutines currently hold backoff state. Done means recent errors for each CT log produce shared, per-process backoff across submitting goroutines, with relevant tests covering the behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- backend, distributed-systems
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 42/100