Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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
Add ConanInvalidConfiguration exception and handle error codes. #3517
Add ConanInvalidConfiguration exception and handle error codes. #3517
Changes from 2 commits
36b210c
369ca34
28aeab5
File filter
Filter by extension
Conversations
Jump to
There are no files selected for viewing
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think that we need a single place to put this hardcoded values, as they are tightly coupled with those documented in the
main
method:There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yes, feel free to move them to global scope, I guess here, in the
command.py
file? Other file?There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I don't like having this message formatted here... any ideas?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think it is consistent to the way exceptions from conanfile.py are managed. Check
_format_conanfile_exception()
, it might be worth to print the line number, etc. in the error message too.Otherwise, if you wanted something specific to configure(), you could try-except the call to
conanfile.configure()
ingraph_builder.py
, but wouldn't be much cleaner either.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I prefer to handle the exception message here, better not pollute the graph code.
This is not an error, is it? so I don't think that adding information about file (it is always
conanfile.py
), or line (always insideconfigure
) adds any information to the caller. It contains the conan ref and the message defined in the recipe, so it should be enough.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I was thinking about lazy
raise ConanInvalidConfiguration("Unsupported platform")
, and which some context, probably seeing the line above could help. But yes, fair, leave it as is, it is good.