[12.x] Remove unnecessary forgetDriver()from TestCaches#58878
Merged
taylorotwell merged 5 commits intolaravel:12.xfrom Feb 16, 2026
Merged
[12.x] Remove unnecessary forgetDriver()from TestCaches#58878taylorotwell merged 5 commits intolaravel:12.xfrom
forgetDriver()from TestCaches#58878taylorotwell merged 5 commits intolaravel:12.xfrom
Conversation
forgetDriver()from TestCachesforgetDriver()from TestCaches
|
Thanks for submitting a PR! Note that draft PRs are not reviewed. If you would like a review, please mark your pull request as ready for review in the GitHub user interface. Pull requests that are abandoned in draft may be closed due to inactivity. |
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
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.
forgetDriver()destroys the resolved store, but classes like the RateLimiter retain a reference to the old instance. This meansCache::clear()clears a new store while the RateLimiter is still counting against the old one.This breaks parallel tests when you clear the cache to reset rate limiters ie the clear essentially does nothing.
The only reason I can think for why this was here is if a cache store was already resolved by another provider — but in that case, forgetting it only makes things worse I guess?
Not sure if it's a B/C ie I couldnt think of a reason, but maybe you can - in which case we can do something like... (rather than just forgetting it blind)
All existing tests still pass and added a regression test to prevent this from being reintroduced.
This closes #58863 if merged :)