Ignore strict match on exception class in rabbit_queue_type_util:erpc_call/5 (backport #16701)#16703
Merged
Merged
Conversation
…_call/5 to ensure all type of exceptions are handled as expected (cherry picked from commit 5e1d1aa)
12 tasks
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.
Proposed Changes
Currently, only an
errorexception class is expected inrabbit_queue_type_util:erpc_call/5- buterpc:call/5can fail withexit, which results in crashes such as below - which are caught but don't matcherrorand still crash. We'd rather just ignore the exception class and avoid these crash terminations/logs and have the expected behavior, e.g. a normal failure on aqueue.declarescenario as below.Types of Changes
What types of changes does your code introduce to this project?
Put an
xin the boxes that applyChecklist
Put an
xin the boxes that apply.You can also fill these out after creating the PR.
This is simply a reminder of what we are going to look for before merging your code.
CONTRIBUTING.mddocumentThis is an automatic backport of pull request #16701 done by [Mergify](https://mergify.com).