Skip to content

This issue was moved to a discussion.

You can continue the conversation there. Go to discussion →

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 seeing reason of version resolution failure #3634

Closed
Nicd opened this issue Sep 20, 2024 · 0 comments
Closed

Allow seeing reason of version resolution failure #3634

Nicd opened this issue Sep 20, 2024 · 0 comments

Comments

@Nicd
Copy link

Nicd commented Sep 20, 2024

In #3002 the reason for version resolution failures was changed to a more simplified version. Example:

➜  aurinko git:(trunk) ✗ gleam deps download
  Resolving versions
error: Dependency resolution failed

An error occurred while determining what dependency packages and
versions should be downloaded.
The error from the version resolver library was:

Unable to find compatible versions for the version constraints in your
gleam.toml. The conflicting packages are:

- aurinko
- mist
- wisp

When you have many packages that have many of their own dependencies, finding out the reason for the failure is not trivial even if it tells you which packages are involved. It would be useful to have a flag --detailed-errors or something like that to allow seeing the admittedly complicated error message that originally existed. I feel that it would be better than nothing. Currently I'm going through Hex.pm, trying to deduce the dependency ranges in my head, but it's difficult as I don't even know which dependency the failure is about.

@gleam-lang gleam-lang locked and limited conversation to collaborators Sep 20, 2024
@lpil lpil converted this issue into discussion #3635 Sep 20, 2024

This issue was moved to a discussion.

You can continue the conversation there. Go to discussion →

Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant