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

Clearer messages when the conflict is caused by strict priority configurations #390

Closed
2 tasks done
jaimergp opened this issue Nov 20, 2023 · 1 comment
Closed
2 tasks done
Labels
stale::closed [bot] closed after being marked as stale stale [bot] marked as stale due to inactivity type::feature request for a new feature or capability

Comments

@jaimergp
Copy link
Contributor

Checklist

  • I added a descriptive title
  • I searched open requests and couldn't find a duplicate

What is the idea?

When the solver cannot find a solution with strict priority enabled, we say PackagesNotFoundError, because the libsolv message is:

Encountered problems while solving:
  - nothing provides requested <package-name>

At that point, libmamba might have thrown several warnings like

warning  libmamba Problem type not implemented SOLVER_RULE_STRICT_REPO_PRIORIT

Which is a hint for some experienced users, but it's not super obvious, and not close to the final message (which is often the only one checked).

Why is this needed?

Better UX when the solver fails to find a solution.

What should happen?

We could decorate the PackagesNotFoundError message with a little hint like "It looks like you have channel_priority set to strict, which can sometimes cause this exception. Consider using flexible for this command using ...".

Additional Context

Comes from https://matrix.to/#/!SOyumkgPRWoXfQYIFH:matrix.org/$170049404134SekiW:gitter.im?via=matrix.org&via=gitter.im&via=staffchat.ethz.ch

@jaimergp jaimergp added the type::feature request for a new feature or capability label Nov 20, 2023
@github-project-automation github-project-automation bot moved this to 🆕 New in 🧭 Planning Nov 20, 2023
Copy link

Hi there, thank you for your contribution!

This issue has been automatically marked as stale because it has not had recent activity. It will be closed automatically if no further activity occurs.

If you would like this issue to remain open please:

  1. Verify that you can still reproduce the issue at hand
  2. Comment that the issue is still reproducible and include:
    - What OS and version you reproduced the issue on
    - What steps you followed to reproduce the issue

NOTE: If this issue was closed prematurely, please leave a comment.

Thanks!

@github-actions github-actions bot added the stale [bot] marked as stale due to inactivity label Nov 20, 2024
@github-actions github-actions bot added the stale::closed [bot] closed after being marked as stale label Dec 20, 2024
@github-actions github-actions bot closed this as not planned Won't fix, can't repro, duplicate, stale Dec 20, 2024
@github-project-automation github-project-automation bot moved this from 🆕 New to 🏁 Done in 🧭 Planning Dec 20, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
stale::closed [bot] closed after being marked as stale stale [bot] marked as stale due to inactivity type::feature request for a new feature or capability
Projects
Archived in project
Development

No branches or pull requests

1 participant