fix(logger): avoid creating new winston instance for each child - #5597
Merged
Conversation
nflaig
commented
Jun 1, 2023
Contributor
Performance Report鉁旓笍 no performance regression detected Full benchmark results
|
wemeetagain
approved these changes
Jun 1, 2023
Member
|
馃帀 This PR is included in v1.9.0 馃帀 |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Motivation
As discussed in #5490 (comment)
Method to create child loggers was updated in
This causes issues with no clear benefit
MaxListenersExceededWarningwhen creating >10 child loggers聽#5529Description
Reverts
logger.childimplementation back to original approachlodestar/packages/utils/src/logger/winston.ts
Line 82 in 375d660
This avoids
MaxListenersExceededWarningwarnings as it no longer creates a new winston instance for each child logger.Reverts #5537 as the workaround is no longer needed.