Logging: Crash if using non default log level names with CloudLoggingHandler #7213
Labels
api: logging
Issues related to the Cloud Logging API.
priority: p2
Moderately-important priority. Fix may not be included in next release.
🚨
This issue needs some love.
type: bug
Error or flaw in code with unintended results or allowing sub-optimal usage patterns.
Environment details
Steps to reproduce
Use GCP logging with non default log level name. Crashes every time. See code below using the non default log level name 'ERR'.
Code example
Output
The text was updated successfully, but these errors were encountered: