Repository navigation
fix(sandbox): let pyenv and rbenv shims run their version manager - #33
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
1 participant
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.
A program on PATH that is a pyenv or rbenv shim failed inside the sandbox: the shim execs the version manager under ~/.pyenv, which the sandbox hid. When a resolved program sits in a
shimsfolder and its script names that folder's parent as its*_ROOT, ghafk now also exposes that parent read-only. A shim that names any other root exposes nothing extra.Found while seeding a Python repository:
uvresolved to ~/.pyenv/shims/uv and the checks failed withpyenv: No such file or directory. With the fix,uv sync --frozen && uv run ruff check . && uv run pytest -qpasses inside the real sandbox, installing from PyPI through the proxy.