handle FileNotFoundError and OSError in _exec (v3.0.0) #126
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.
Change Summary
This PR handles
FileNotFoundandOSErrorexceptions in_exec, because they started existing and not being caught inv3.0.0.I'm open to other opinions about what should be returned as
stdout, but I figured the actual code change was minimal enough not to create a separate issue.Details
v3.11v3.0.0In the
v3.0.0release, I started getting some uncaughtFileNotFoundErrorexceptions duringuv sync.It seems related to the change from passing
shell=Trueto defaulting toshell=False-- the Exception type changes when a command isn't found, and we don't catch it currently.In particular, I'm using the
ghcr.io/astral-sh/uv:0.8-python3.11-bookworm-slimdocker image, which doesn't havegitinstalled. I was not seeing the errors before, but suddenly broke around 1pm PT today, lining up with cuttingv3.0.0.stack trace from
uv sync:Related issue number
Checklist
docs/changelog/next_release/<pull request or issue id>.<change type>.rstfile added describing change(see CONTRIBUTING.rst for details.)