impr(api): add automatic recovery if API panics on a call - #1179
Merged
Conversation
pandatix
added
go
|
The latest Buf updates on your PR. Results from workflow CI / buf-lint (pull_request).
|
Pull Request Test Coverage Report for Build 20853227625Details
💛 - Coveralls |
NicoFgrx
approved these changes
Jan 9, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This PR adds a simple safety measure to avoid availability loss in case an API call make CM panics.
Currently, if something panics on an API call the whole service stops. In case the hosting platform does not recover (e.g. Kubernetes does so, not Docker Compose), the service becomes unavailable. This might be used by attackers to DoS CTF infrastructures.