-
Notifications
You must be signed in to change notification settings - Fork 27
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
Improve error messages when the solver fails #154
Comments
I have a proof of concept that is able to improve the quality of error messages by grouping identical messages together. It's actually a patch in What do you think @NathanReb @Leonidas-from-XIV ? An example, trying to lock Before
After
|
Compacting the information does look much nicer indeed! Thanks for working on this! In particular, I assume this remove the annoying This definitely looks like a step in the right direction. We haven't had time to look into error messages on our end but this is on the roadmap. I think something that could be done in opam-monorepo is to prioritize things a bit, e.g. by only showing a reduced set of "problems", selecting the ones that are most relevant to the user. It might be nice if you could expose parts of this in Either way we'll always need a fallback when there's nothing obvious to show and so having a nicer full error report is very important. |
@TheLortex were you able to submit a patch upstream for this? |
opam-monorepo
has a very verbose error log when failing to solve packages. Its notably hard to distinguish the failing packages from the others.For the same set of dependencies, here are the outputs of
opam
andopam-monorepo
, where the failing packages are:mirage-kv
that has to be < 3.0.0 and >= 3.0.0uri < 1.9.4
,lwt < 3.0.0
, ... that require old versions of the ocaml compileropam
opam-monorepo
The text was updated successfully, but these errors were encountered: