fixed build pipline. error: logger log lvl set in an outdated way #12
Conversation
This file contains 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
…nge.sh moved -v flag to create_package.py
BigRoy
approved these changes
Jun 21, 2024
There was a problem hiding this comment.
Didn't test but code changes make sense.
The bugs being fixed also match the report on Ynput discord here
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.
The development branch has two bugs in the
create_package.pyandmanage.shrespectively.manage.shis callingcreate_package.pywith the-vflag; this option is no longer available and can be removed.create_package.pytries to create the logger instance with the log level parameter, but that needs to be done via setLevel()