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
{{ message }}
This repository was archived by the owner on Jun 15, 2021. It is now read-only.
Logger seems to affect the way go's log works and redirects output to the default output which is Stdout. Default output for log is Stderr. There are couple of questions:
Should logger affect how other packages work?
If Yes should user be given option to disable this behaviour?
Should default for logger be Stdout? Stderr seems to be more appropriate output stream
We should have an option to silence initial log messages. Ideally they should use logger framework and not go's log
The way it works now affect how other can integrate with flyte. For example when you are trying to use flyte as dependency in your project logger package will be imported and init method will be executed and might result in unpredictable behaviour of log package or not gonna allow to silence logs for output.
The text was updated successfully, but these errors were encountered:
Logger seems to affect the way go's
log
works and redirects output to the default output which is Stdout. Default output forlog
is Stderr. There are couple of questions:logger
framework and not go'slog
The way it works now affect how other can integrate with flyte. For example when you are trying to use flyte as dependency in your project logger package will be imported and init method will be executed and might result in unpredictable behaviour of log package or not gonna allow to silence logs for output.
The text was updated successfully, but these errors were encountered: