-
-
Notifications
You must be signed in to change notification settings - Fork 210
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
fix: re-use file transport instance when setup loggers #3928
Conversation
Pull Request Test Coverage Report for Build 11382649159Details
💛 - Coveralls |
I haven't tested yet, but what about other transports? Shouldn't console and stream transports be created only once as well? |
@spudwebb good point, I focused on the filetransport but it makes sense to extend this to all transports list. Just submitted the fix |
With this branch I now get the followings warnings in the console when I start ZUI
Here is what I get when I use --trace-warnings:
|
@robertsLando I confirm that with this branch the original error I got at midnight when the files rotate is gone, but as stated above I now get a |
@spudwebb I will fix this asap, give me some time as I'm very full in this period |
@robertsLando I'm not sure there is anything wrong with the way you implemented this. These warnings appear because of the number of module loggers in ZUI which now triggers the default 10 limit on event listeners on So if I do the same thing in the
|
@spudwebb Sorry, just found some time to look at this again, release is coming. Thanks again for your help 🙏🏼 |
Fixes #2937