Repository navigation
recover from panics in http handlers - #973
Merged
Merged
Conversation
A panic in a handler goroutine used to abort the connection without a response (502 on the load balancer), and a panic in a goroutine spawned by a handler crashed the whole process. - add a recovery middleware that logs the panic, counts it and responds with HTTP 500 - run goroutines spawned by handlers with conc.WaitGroup so their panics are propagated to the request goroutine - recover in mempool emulation goroutines - fix a data race on err in spam filter goroutines Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
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
1 participant
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.
A panic in a handler goroutine used to abort the connection without a response (502 on the load balancer), and a panic in a goroutine spawned by a handler crashed the whole process.