Fix a double-panic when static methods' expectations are oversatisfied #516
Conversation
This file contains 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
PR #443 ensured that static methods' expectations would be cleared on Drop. But it was only tested for methods that paniced due to too few method calls. For methods with too many calls it actually introduced a double-panic. Double panics are bad; they lead to processes getting SIGABRT. This was a regression in Mockall 0.11.4. Fixes #491
|
@msr1k does this change work for you? |
|
I noticed this mention now. Okay, I will check it. |
|
No problem, it worked! Thanks. |
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.
PR #443 ensured that static methods' expectations would be cleared on Drop. But it was only tested for methods that paniced due to too few method calls. For methods with too many calls it actually introduced a double-panic. Double panics are bad; they lead to processes getting SIGABRT. This was a regression in Mockall 0.11.4.
Fixes #491