Stop reporting errors when no service instance is available#643
Merged
Conversation
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
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.
Summary
ServiceInstance.pick!raises, flooding Honeybadger (fault #130263597, 5,243 notices) for what is an expected, recurring condition.ServiceInstance.pick!now raises a dedicatedServiceInstance::NoInstanceAvailableErrorinstead of a bareRuntimeError, so callers can tell an empty pool apart from a genuine fetch failure.RedditProcessor#scorerescuesNoInstanceAvailableErrorand silently returns0. Real fetch errors (HTTP failures etc.) are still reported viaHoneybadger.notify.Checklist
CHANGELOG.mdunderUnreleased, or change is internal-only