Uh oh!
There was an error while loading.Please reload this page.
- Notifications
You must be signed in to change notification settings - Fork9.7k
[Messenger] DispatchAfterCurrentBusMiddleware does not cancel messages from delayed handlers#32497
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to ourterms of service andprivacy statement. We’ll occasionally send you account related emails.
Already on GitHub?Sign in to your account
Merged
Uh oh!
There was an error while loading.Please reload this page.
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
maidmaid approved these changesJul 11, 2019
Member
weaverryan commentedJul 14, 2019
Wdyt@Nyholm? |
sroze approved these changesAug 18, 2019
Contributor
sroze left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others.Learn more.
Nice fix to a quite complex problem 👍
Member
fabpot commentedAug 18, 2019
Thank you@BastienClement. |
fabpot added a commit that referenced this pull requestAug 18, 2019
…cel messages from delayed handlers (Nyholm, BastienClement)This PR was merged into the 4.3 branch.Discussion----------[Messenger] DispatchAfterCurrentBusMiddleware does not cancel messages from delayed handlers| Q | A| ------------- | ---| Branch? | 4.3 for bug fixes| Bug fix? | yes| New feature? | no| BC breaks? | no| Deprecations? |no| Tests pass? | yes (thanks@Nyholm)| Fixed tickets |#32370| License | MIT| Doc PR | -This is a fix for#32370. There is no need for anything sophisticated. There is no recursion or fancy stuff going on, just a queue of message handled sequentially. A simple variable is enough to keep track of the queue state.Thanks@Nyholm for the test, it would clearly have been the hardest part of the job.Commits-------1f5c8a6 Cancel delayed message if handler fails35c76a3 Added tests for#32370
Merged
Sign up for freeto 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.
This is a fix for#32370. There is no need for anything sophisticated. There is no recursion or fancy stuff going on, just a queue of message handled sequentially. A simple variable is enough to keep track of the queue state.
Thanks@Nyholm for the test, it would clearly have been the hardest part of the job.