You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
By default our structlogs are printing debug messages, which are quite noisy. The standard pattern of setting log levels using the logging library isn't being respected, thus it's hard to know how to tune the second config of logging present.
To Reproduce
Steps to reproduce the behavior:
Run any notebook
See debug logs
Change logging level
Still see debug logs
Change structlog levels
See debugs go away
Expected behavior
The papermill cli and logging library levels should be the defaults when starting struct logs. We may need to scan log levels and pass them along when we initialize structlog.
The text was updated successfully, but these errors were encountered:
Describe the bug
By default our structlogs are printing debug messages, which are quite noisy. The standard pattern of setting log levels using the logging library isn't being respected, thus it's hard to know how to tune the second config of logging present.
To Reproduce
Steps to reproduce the behavior:
Expected behavior
The papermill cli and logging library levels should be the defaults when starting struct logs. We may need to scan log levels and pass them along when we initialize structlog.
The text was updated successfully, but these errors were encountered: