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.
Summary
It looks like the issue here is that the workflow was missing
actions/setup-python
. Without it, I think the workflow has access to Python in the "tool cache" but that it's like... not fully configured? So you don't have write permissions to it?pip
has a behavior whereby if you try to install, and you don't have permissions to write, it falls back to a slightly different setup (as if you ranpip install --user
). We don't have that behavior inuv
. But if you usesetup-python
(is 0 seconds anyway), then the workflow will have the expected permissions, anduv pip install --system
works withoutsudo
.Test Plan
docker build .
locally