-
Notifications
You must be signed in to change notification settings - Fork 2.5k
Incorrect logging level for oauth2client.contrib.locked_file
(ref #427)
#873
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
Comments
Simply removing |
Same/similar issue here. Getting the following when instantiating a Google Drive client:
This is causing issues in our monitoring stack because we consider logs with 'Traceback' in them to be unhandled exceptions and this warning message results in false positives. So far my solution has been to lock |
Any idea when this might be merged? The log output takes up way too much space and occurs way too frequently (every search causes it to be repeated), which just makes logs a chore to go through. I can understand showing all of this in the first search but repeating it every time is just annoying. |
I've used the method proposed by @davidcpell to lower the oauth2client to 1.5.2, which works well. However, an exception is generated if I have logging turned on in our code when using the latest version of the oauth2client. |
@mysticaltech Thank you. That worked well! |
Linking #1061 as it is related. |
This is - as per request in the original #427 - a follow-up issue.
The function documentation says:
Exceptions in this context only provide a pythonic way to do control flow, and do not indicate anomalies or malfunctioning of the code.
None
is a perfectly fine, as-per-specifications behaviour. The correct level should probably beINFO
.Also, even if you would stand by the
WARNING
level, you should tidy up the messy log message. This is what the user is met with:A saner way to to communicate with the user could potentially be:
WARNING - No caching available (file_cache is unavailable when using oauth2client >= 4.0.0 or google-auth)
The text was updated successfully, but these errors were encountered: