Repository navigation
Fix cache compatibility and reduce mutable kernel hashing - #6
Merged
Merged
Conversation
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.
Warm mutable requests no longer hash each consumed configuration file twice. Content validation still detects same-mtime replacements and imported-resource changes; complete elimination of mutable-content reads requires the documented immutable build-ID policy.
Existing installations with group-writable compiled-cache directories boot through a fresh private cache generation. Prior PHP dumps and directory permissions are preserved, and explicit publicly served cache paths remain rejected. Prepare patch 1.1.2.
Validation:
composer qapassed (70 tests/337 assertions, CS/PHPStan; seven existing PHPUnit notices). New tests reproduce the original failures and exercise successive fresh PHP processes. Runtime container/lint checks passed. A fixture benchmark with 8 MiB configuration and 2 MiB lock (20 fresh requests per state) measured median 15.52 to 10.21 ms and configuration reads 2 to 1. This is fixture performance evidence, not a production latency claim.