You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
See that after quite a time the error bloats up in a tremendous number of failures in the logs
Possible Solution
In case when $this->maxDelayMilliseconds is configured (2 hours in the above example), it would make sense not to calculate the hypothetical delay that could've been in case if that option was absent.
Additional Context
No response
The text was updated successfully, but these errors were encountered:
…ng delays (alexandre-daubois)
This PR was merged into the 7.1 branch.
Discussion
----------
[Messenger] Prevent waiting time to overflow when using long delays
| Q | A
| ------------- | ---
| Branch? | 7.1
| Bug fix? | yes
| New feature? | no
| Deprecations? | no
| Issues | Fix#57779
| License | MIT
There are two places where integers can overflow, thus the limiting to `PHP_INT_MAX`.
Commits
-------
9609e23 [Messenger] Prevent waiting time to overflow when using long delays
Symfony version(s) affected
7.1
Description
Currently we face following error:
It seems that
$randomness
is overflowed in such way that it becomes a negative integer.Hence,
random_int
stumbles over it:How to reproduce
Possible Solution
In case when
$this->maxDelayMilliseconds
is configured (2 hours in the above example), it would make sense not to calculate the hypothetical delay that could've been in case if that option was absent.Additional Context
No response
The text was updated successfully, but these errors were encountered: