fix: configurable node-local verifier cache - #2561
Draft
samsja wants to merge 1 commit into
Draft
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.
Support VERIFIERS_CACHE_DIR (including ~ expansion) so large local eval runs can keep verifier cache lookups off shared NFS. The default remains ~/.cache/verifiers; an empty override retains the default.
Validation: Ruff and direct default/absolute-path/tilde-override assertions pass. This is a cache-root selection change, not a concurrency limiter or an NFS filesystem fix.
Note
Add
VERIFIERS_CACHE_DIRenvironment variable override for verifier cache pathAdds a new
cache_dirresolver in paths.py that expandsVERIFIERS_CACHE_DIRwhen set, otherwise falls back to the existing temporary-home-based default. The module-levelCACHE_DIRnow initializes through this resolver at import time.Macroscope summarized d4f446e.