-
Notifications
You must be signed in to change notification settings - Fork 988
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 messages expose a dependency relationship between a
and a{marker}
#5618
Labels
bug
Something isn't working
error messages
Messaging when something goes wrong
resolver
Related to the package resolver
Comments
BurntSushi
added
bug
Something isn't working
error messages
Messaging when something goes wrong
resolver
Related to the package resolver
labels
Jul 30, 2024
Seems clearer than #5612 |
Haha whoops! Totally missed that one. |
Does anyone have an example that produces this? |
I think pretty much anything that doesn't produce a resolution and involves markers will do:
Although I suppose this will stop producing an error once overlapping marker support lands. :P |
Awesome thank you :) I was having trouble getting this exact form to appear. |
charliermarsh
added a commit
that referenced
this issue
Aug 2, 2024
## Summary If _both_ nodes in the derivation tree are proxies, we need to remove the _entire_ node. So, the function now returns an `Option<Tree>` instead of taking `&mut Tree`. Closes #5618.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
bug
Something isn't working
error messages
Messaging when something goes wrong
resolver
Related to the package resolver
For example:
Specifically:
If one is familiar with internals, this makes sense, because we have specific "marker" dependencies and "normal" dependencies, and they have a dependency relationship with one another. But from an end user perspective, they probably should be treated as just one package.
The text was updated successfully, but these errors were encountered: