-
-
Notifications
You must be signed in to change notification settings - Fork 9.6k
[HttpKernel] Don't cache "not-fresh" state #34580
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
nicolas-grekas
commented
Nov 25, 2019
Q | A |
---|---|
Branch? | 4.4 |
Bug fix? | yes |
New feature? | no |
Deprecations? | no |
Tickets | Fix #34567 |
License | MIT |
Doc PR | - |
It fixed the issue, thanks! |
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.
same 👍
I'd appreciate 4.4.1 could be tagged as soon as this patch is merged 🙏 |
Thank you @nicolas-grekas. |
This PR was merged into the 4.4 branch. Discussion ---------- [HttpKernel] Don't cache "not-fresh" state | Q | A | ------------- | --- | Branch? | 4.4 | Bug fix? | yes | New feature? | no | Deprecations? | no | Tickets | Fix #34567 | License | MIT | Doc PR | - Commits ------- be80db3 [HttpKernel] Don't cache "not-fresh" state
@nicolas-grekas shouldn't we also mark the cache as fresh after we rebuild it ? |
@stof I considered this but thought it was not needed - this would only save one extra freshness check - with little to no perf benefit. |