Run the 24h production soak + curated error allowlist (release gate, from #182)
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 35
- Forks
- 4
- Avg merge
- 17h 19m
- Merged PRs (30d)
- 8
Description
Question
Part of #200 (map). The last unresolved item of the #182 map (all its execution tickets have landed): read 24h of production logs across all three bots, curate the allowlist of accepted error/WARN classes, and declare zero-unexplained. This is the release-readiness gate.
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.
Research direction
Start by reading issues #182 and #200 to understand the release map and the execution tickets that have landed. Observe 24 hours of production logs across all three bots, curate the accepted error and WARN classes, and consider the work done when every remaining message is explained and zero unexplained items can be declared.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- observability-sre, release
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 38/100