Repository navigation
🐛 fix(cache): retry after cache I/O errors - #216
Merged
gaborbernat merged 3 commits intoNov 3, 2026
Merged
Conversation
POSIX cache locks moved under locks-v2 after this branch started. Block the lock path used on each platform so the recovery test still exercises a cache I/O failure.
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.
from_exe()let cache filesystem errors escape interpreter discovery. An unusable cache entry or lock could stop a lookup even when the interpreter itself was available. Discovery now retries without the supplied cache after a cache I/O error. Fixes #187.Cache errors stopped the lookup
The previous cache path held the lock, read the entry, queried the interpreter, and wrote the result. A filesystem error during that path propagated to the caller. The new
from_exe()handling retries through the uncached path after anOSError. The original lock is not bypassed for a cache write; the retry uses no disk cache.Behavior changes
An unusable cache no longer prevents discovery of a working interpreter. A failed cache write can cause a second interpreter query. The uncached retry returns the interpreter result or its normal query error. Calls with caching disabled keep their existing error behavior.
Reported by Anthropic's OSS Scanner: ANT-2026-6N6E3MNU.