Repository navigation
Align cached HTTP policies within the payload buffer - #22079
Merged
charliermarsh merged 1 commit intoSep 30, 2026
Merged
charliermarsh merged 1 commit into
charliermarsh merged 1 commit into
Conversation
charliermarsh
had a problem deploying
to
automations
September 29, 2026 17:42 — with
GitHub Actions
Error
charliermarsh
force-pushed
the
charlie/align-http-cache-policy
branch
from
September 29, 2026 17:50
fa4874b to
d57d28c
Compare
charliermarsh
marked this pull request as ready for review
September 29, 2026 17:50
charliermarsh
temporarily deployed
to
automations
September 29, 2026 17:52 — with
GitHub Actions
Inactive
Merging this PR will not alter performance
Comparing Footnotes
|
Member
|
|
charliermarsh
force-pushed
the
charlie/align-http-cache-policy
branch
from
September 30, 2026 01:43
d57d28c to
6d2c0b6
Compare
charliermarsh
temporarily deployed
to
automations
September 30, 2026 01:45 — with
GitHub Actions
Inactive
charliermarsh
added a commit
that referenced
this pull request
Oct 1, 2026
We revert the cache-format stack so `main` retains the 0.12 cache formats and bucket versions. These changes are deferred to 0.13. This reverts the following PRs together, including the six cache bucket bumps and the serialization and Windows lock-name changes that depend on them: - #22052: Refresh HTTP cache policies in place - #22059: Store source distribution revision IDs inline - #22060: Remove the legacy hash digest cache representation - #22061: Derive serialization for cached artifact records - #22062: Use bounded wheel cache lock names on Windows - #22078: Pack HTTP cache policy flags and optional integers - #22079: Align cached HTTP policies within the payload buffer
charliermarsh
added a commit
that referenced
this pull request
Oct 1, 2026
Reapplies #22079 for 0.13. We align HTTP cache policies within the payload buffer and access them directly after validation, removing a separate allocation and copy from every cache read. Extracting the payload reuses the same allocation. The file adds up to 15 bytes of padding, covered by the CRC32. Policy validation is restricted to its own slice, and refreshes retain the entry ID check before overwriting the policy.
zanieb
pushed a commit
that referenced
this pull request
Oct 7, 2026
Reapplies #22079 for 0.13. We align HTTP cache policies within the payload buffer and access them directly after validation, removing a separate allocation and copy from every cache read. Extracting the payload reuses the same allocation. The file adds up to 15 bytes of padding, covered by the CRC32. Policy validation is restricted to its own slice, and refreshes retain the entry ID check before overwriting the policy.
zanieb
pushed a commit
that referenced
this pull request
Oct 9, 2026
Reapplies #22079 for 0.13. We align HTTP cache policies within the payload buffer and access them directly after validation, removing a separate allocation and copy from every cache read. Extracting the payload reuses the same allocation. The file adds up to 15 bytes of padding, covered by the CRC32. Policy validation is restricted to its own slice, and refreshes retain the entry ID check before overwriting the policy.
astral-automations-bot Bot
pushed a commit
to astral-sh/uv-dev
that referenced
this pull request
Oct 10, 2026
Reapplies astral-sh#22079 for 0.13. We align HTTP cache policies within the payload buffer and access them directly after validation, removing a separate allocation and copy from every cache read. Extracting the payload reuses the same allocation. The file adds up to 15 bytes of padding, covered by the CRC32. Policy validation is restricted to its own slice, and refreshes retain the entry ID check before overwriting the policy.
This branch was previously deployed
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.
We align HTTP cache policies within the payload buffer and access them directly after validation, removing a separate allocation and copy from every cache read. Extracting the payload reuses the same allocation.
The file adds up to 15 bytes of padding, covered by the CRC32. Policy validation is restricted to its own slice, and refreshes retain the entry ID check before overwriting the policy.