-
-
Notifications
You must be signed in to change notification settings - Fork 649
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
FileExistsError
while building requirements.pex
#15862
Comments
pypa/cibuildwheel#813 has some discussion of what looks like the same error. It was closed with a work-around - not sure if any of the discussion could apply to Pants / pex |
The work-around Pip option is plumbed through PEX and that is:
It looks like Pants does not plumb this though. You might also try https://www.pantsbuild.org/docs/reference-python#section-macos-big-sur-compatibility but that almost certainly won't help. |
@danxmoran If you want to dig here on the machine where the problem occurs, the steps would be:
Where That should hopefully just reproduce the error, but with Pants removed. Then try:
If this fixes things, then we can move on to considering how to plumb this Pex option through Pants. |
Just realized this was the very first time we saw pex-tool/pex#2025 |
Some of our devs hit this issue consistently on M1 Mac. The issue went away after they removed all python versions and installed only 3.9.16 using pyenv. |
Going to close this one as it seems like a problem with the underlying dependencies, not Pants |
Describe the bug
While running
./pants lint <dir>
, a teammate is hitting:Unfortunately others haven't been able to reproduce 😞 but it looks like a potential race condition coming out of
pex
.Pants version
PANTS_SHA=19fe4e3cec21067791dea8f1351c033c7132f579
(living dangerously so we can try out the improvements / new features slated for 2.13)
OS
MacOS
Additional info
The day we jumped to the 2.13 prerelease was (unfortunately) the same day Pants was added by default to many eng workflows at my company, so it's unclear to me if this problem is new to Pants 2.13 or if it's always been there and we just haven't had enough people running Pants to hit it. We're still debugging on our end.
The text was updated successfully, but these errors were encountered: