-
Notifications
You must be signed in to change notification settings - Fork 614
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
uv sync --no-source
breaking from 0.4
#7572
Comments
This is a complicated one, because |
Yeah this seems like a bug? We should not be trying to use the source entry from the lockfile when At the very least, the error message is horrible. What's the suggestion if we were to keep the existing behavior and just improve the error? To run |
I think there's a bug because we shouldn't even be trying to resolve the sources here (which is where the failure happens). |
@charliermarsh
Weirdly the uv sync works, it is when it goes to the next RUN command that it fails |
You'd have to pass |
ah okay, thank you for the quick reply <3 |
Hello,
My basic TOML:
In UV 0.3.5 this worked for me:
docker build .
Output:
[+] Building FINISHED
In UV 0.4.13 it doesn't work anymore:
Output:
My setup is a workspace with 3 parts: two app (
pythia-streamlit
,pythia-api
) and a python package (pythia-client
). The Dockerfile snippet is coming from production image where I want to installpythia-client
from Pypi. In local developement environnement I remove the--no-sources
to install from local folder (from parent directory).The update from 0.4 broke by CI/CD pipeline, because the image would not build anymore due to the error above.
Any idea why ?
The text was updated successfully, but these errors were encountered: