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

Unlucky sorting of "Possible values are..." error message #8571

Closed
AlexanderLanin opened this issue Feb 28, 2021 · 2 comments · Fixed by #8573
Closed

Unlucky sorting of "Possible values are..." error message #8571

AlexanderLanin opened this issue Feb 28, 2021 · 2 comments · Fixed by #8573
Assignees
Labels
complex: low component: ux No changes to core business logic type: feature
Milestone

Comments

@AlexanderLanin
Copy link

Environment Details (include every applicable attribute)

  • Operating System+version: Ubuntu 20.04 in WSL2
  • Compiler+version: clang version 10.0.0-4ubuntu1
  • Conan version: 1.34.0
  • Python version: 3.8.5

Steps to reproduce

For pretty much any package run conan install .. -s compiler=clang -s compiler.version=10.0

Logs (Executed commands with output) (Include/Attach if Applicable)

ERROR: Invalid setting '10.0' is not a valid 'settings.compiler.version' value.
Possible values are ['10', '11', '3.3', '3.4', '3.5', '3.6', '3.7', '3.8', '3.9', '4.0', '5.0', '6.0', '7.0', '7.1', '8', '9']
Read "http://docs.conan.io/en/latest/faq/troubleshooting.html#error-invalid-setting"

Expected behavior

Sort either by increasing number or as in settings.yml (most likely someone sorted it there intentionally).
I though conan is totally out of date since the latest version is 9.
It took me quite a while to notice the 10 and 11 at the beginning.
In settings.yml they are at the end:

    clang:
        version: ["3.3", "3.4", "3.5", "3.6", "3.7", "3.8", "3.9", "4.0",
                  "5.0", "6.0", "7.0", "7.1",
                  "8", "9", "10", "11"]
@memsharded
Copy link
Member

Lets see in #8573, if it is possible to keep the original order of the lists. It is possible that something might break that might be relying on this order, but lets see.

@memsharded
Copy link
Member

Changed in #8573, will be released 1.35

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
complex: low component: ux No changes to core business logic type: feature
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants