Conversation
|
Hey again! Thanks for taking the time for this PR. I will take a closer look with Jeremy sometime this week, but at first glance this looks great!
Both of these are good points that seem right to me! |
|
Hello, |
|
Hi @dhia-gharsallaoui, thanks for the PR! My only issue with it is the global mutable state of the logger. But, for something like this, I think that's relatively minor. We can refactor it if it becomes an issue. |
| blocking: Blocking.Service => new Logging.Service.Default(System.err, blocking) | ||
| } | ||
|
|
||
| object Verbosity extends Enumeration { |
There was a problem hiding this comment.
Not a big fan of Enumeration but I guess it gives you the ordering for free in this case.
|
Thank you for the review @jeremyrsmith ! |
|
Thanks @dhia-gharsallaoui for the PR. I think it's OK not to deal with remote logs for now. A nice thing to do would be to configure files for log output, and have separate files for each kernel's (like remote logs) vs the polynote server's logs. |
Hello 👋
This PR add the possibility to configure the logger verbosity using the configuration file.
the default value is
Infoto keep the old default behavior.In addition, I set the verbosity after logging the configuration, securityWarning, polynote banner and the version. What do you think about that?
this PR is done with the love and the help of @ahuret and @skilld-labs