-
Notifications
You must be signed in to change notification settings - Fork 1k
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
Error with URL requirements and pip variables #8353
Comments
If we ignore the url, then we'll be ignoring constraints during the update and may end up proposing updates incompatible with the project. I think we need to fetch all constraints to make sure we don't break projects. Can you verify whether the URL without an ENV works? If it does not, then that's a bug we should fix. Regarding the ENV itself, supporting that kind of thing would fall under #4660 I believe. |
I just created a test repo with the following content:
and the same error appears:
The problem is that even if you fix the URL handling, dependabot will try to fetch the URL without the replaced variable, which will obviously fail and the error in my case will persist. I don't need the variable expansion, it would already help if dependabot ignored requirements which it knows it can't fetch, like ones containing pip variables. Yes, some incompatible updates might be suggested, but that would be better than not being able to use dependabot at all. Also, in my case, I have control over both repositories, so I can update them both at once to prevent incompatible versions alltogether. |
I think it's better to not create PRs at all than potentially creating incompatible PRs. People don't like it when Dependabot creates PRs that break their CI, or even worse, their apps. If we allowed this, it would certainly get reported as a bug eventually. I think we should eventually support ENV variables to satisfy cases like yours. I recommend you watch #4660. I'll leave this issue open to track the URL handling problem. Thanks for reporting and testing this! |
Is there an existing issue for this?
Package ecosystem
pip
Package manager version
No response
Language version
No response
Manifest location and content before the Dependabot update
DATASTORE_COMMIT_HASH
is filled beforehand by a script.dependabot.yml content
Updated dependency
No response
What you expected to see, versus what you actually saw
Dependabot broke down with the following error and did not create any update PRs for any dependency, although some need updating:
Instead, such a line should simply be ignored. I'm not sure if the URL or the variable in the URL is the problem, but both should be relatively to filter out.
Native package manager behavior
No response
Images of the diff or a link to the PR, issue, or logs
No response
Smallest manifest that reproduces the issue
No response
The text was updated successfully, but these errors were encountered: