Convert COG_LOG_LEVEL=warning to use "warn" so zap can parse it
#210
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.
Cog sets
COG_LOG_LEVEL=warningwhen running predictors.Python's logger (used before cog-runtime came along) can parse
warning,WARNING,warn,WARNzap only acceptswarn,WARN.This difference is causing
Failed to parse log level "warning": unrecognized level "warning"to show up in user-facing logs.We can fix the issue in cog, but we'd still have differences in behavior depending on the version of cog, cog-runtime, or cog-python being used. So safest thing is to normalize it here.