fix: ValueError: Unknown level: 'LOGLEVEL.WARNING'
#2249
Merged
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
fubuloubu
previously approved these changes
Aug 27, 2024
|
so this didn't fix it yet! but no worries, trying something else |
|
OK verified the bug is fixed. stomped out of existence. |
fubuloubu
approved these changes
Aug 27, 2024
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.
What I did
Fix the bug in 3 spots because am mad:
LogLevelvalues with LogLevel prefix everywhere.valueinape testbecause is more performant and makes more sense and you don't run into weird issues in some CI/CD environments.-v(in case it is ending up in there)How to verify it
ApeWorX/ApePay#99
Checklist