Set 'metadata-caching: 0' as default #16
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
hasufell
force-pushed
the
metadata-caching
branch
4 times, most recently
from
2e417e2 to
1283828
Compare
Member
Author
|
Even with file caching disabled... we're reasonably fast due to using etags. |
hasufell
force-pushed
the
metadata-caching
branch
from
1283828 to
5957565
Compare
andreabedini
approved these changes
Apr 7, 2025
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.
This was discussed with @TerrorJack in the wasm channel: a user switching URLs (as in: e.g. two different commits of the same metadata file) between steps on a mutable private runner may not see the effects, because GHCup has a 600s caching based on last modification time of the file