[8.x] Make sure availableIn returns positive values #37809
Merged
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.
Problem
When running a job on Laravel Vapor if a rate limiter middleware is added to that job, like below
The following error message from SQS pops up in the logs intermittently.
I tracked down the problem to
Illuminte\Cache\RateLimiter::availableIn
where it can some times return negative values apparently when a "timer" value is not yet set in the cache. (I guess this only happens under heavy loads)I was able to spot one in the wild when that happens. Here's an example:
Solution
Make sure
availableIn
always return a positive value. This wayIlluminate\Queue\Middleware\RateLimited::getTimeUntilNextRetry
can return an appropriate value.Perhaps
Illuminate\Queue\Middleware\RateLimitedWithRedis::getTimeUntilNextRetry
requires a similar prevention? Let me know if you think it does and I can work on it as well.