FIX: fixed get_log_level when level = 3#346
Merged
adrinjalali merged 2 commits intoskops-dev:mainfrom Oct 12, 2023
Merged
Conversation
BenjaminBossan
approved these changes
Apr 20, 2023
Collaborator
BenjaminBossan
left a comment
There was a problem hiding this comment.
LGTM, thanks for catching this. Ping @E-Aho
This comment was marked as off-topic.
This comment was marked as off-topic.
Contributor
Author
|
HI @jot-s-bindra , I am happy to help! |
adrinjalali
approved these changes
Oct 12, 2023
Collaborator
|
@adrinjalali Feel free to merge, I think this one just slipped under the radar. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
When working on #343, I stumbled upon this tiny bug: if one sets the log level equal to 3, the CLI raises a
IndexErrorexception.Steps to reproduce:
I added the fix in this PR and also a small test. :)