feat(interactive): All checks should be removed from interactive code.
Open
- Dominant language
- C++
- Stars
- 3.6k
- Forks
- 468
- Avg merge
- 29m
- Merged PRs (30d)
- 1
Description
`CHECK(...)` failure will cause process termination. Since interactive is supposed to be providing service stably, all `CHECK`s should be removed.
Contributor guide
Research direction
Start by locating the interactive code and every CHECK(...) use within it. Review how each failure is currently handled, then verify that no CHECK remains in the interactive path and that failures no longer terminate the service.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- distributed-systems
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100