Skip to content
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

Allow returning "unknown dependencies" in get_dependencies #17

Merged
merged 1 commit into from
Jan 25, 2024

Conversation

aochagavia
Copy link
Contributor

@aochagavia aochagavia commented Jan 24, 2024

Note: this assumes #15 and #16 are merged.

Question: should we make it possible for the provider to tell the reason why the dependencies are unknown? For instance, a string where we can put the contents of this panic

Closes #14

@baszalmstra
Copy link
Contributor

You are on 🔥! And yes to the question! Because that would be ideal to show in a unsat report

@aochagavia
Copy link
Contributor Author

All right, just pushed the changes.

And here's a diff showing how it looks like in rip.

@Eh2406
Copy link

Eh2406 commented Jan 24, 2024

BTW, I am hoping to add a user customizable error string for unknown dependencies in pubgrub. So I think it is a good idea here too!

@wolfv
Copy link
Member

wolfv commented Jan 24, 2024

Nice work @aochagavia! :) Let's get your PRs reviewed and merged tomorrow 🚀

This makes it possible for a DependencyProvider to signal that it failed
to retrieve a solvable's depenencies (instead of crashing). The
consequence is that the original solvable is marked as excluded.
@tdejager tdejager merged commit f253121 into mamba-org:main Jan 25, 2024
3 checks passed
@aochagavia aochagavia deleted the tweak-dependency-provider branch January 25, 2024 10:37
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Exclude candidates in get_dependencies of the DependencyProvider
5 participants