-
-
Notifications
You must be signed in to change notification settings - Fork 9.6k
[Messenger] Fix stopwach usage if it has been reset #39598
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 our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
Can you please add a test case? |
@lyrixx i plan to do the same thing on a personal project very soon, thx |
@nicolas-grekas Sure, i'll do :) @noniagriconomie It occurs in dev as I said
So I notice that in dev. I do not replace things in prod directly (yet) :) (huhu, this is a joke, no offence) |
27bda76
to
d0e1de8
Compare
6b8456d
to
3e05325
Compare
@lyrixx sorry I found no trace of this in the PR desc :s, thus my question :) |
src/Symfony/Component/Messenger/Middleware/TraceableMiddleware.php
Outdated
Show resolved
Hide resolved
3e05325
to
bf4b0cc
Compare
Thank you @lyrixx. |
I'm slowly migrating an application to messenger (from swarrot) and I
hit a strange bug. My message was well processeed BUT retry!
It comes from two things
low memory usage)
stopwatch has been reset, an exception occurs and the message has been
retried
So this patch avoid throwing an exception when everything works well
the trace: