Loggers miss the requestId
Because requestId is now an (optional) constructor argument of LogManager, but LogManager is instantiated by the bootstrap
first without this argument, the requestId remains empty.
The LogManager is indirectly instantiated the first time when error handling is set up and a logger is injected into ErrorHandler
[BUGFIX] Ensure LogManager has requestId set
Since LogManager is first used when ErrorHandler is instantiated,
we need to provide a properly set up singleton before
setting up error handling.
Tested-by: Benjamin Franzke <firstname.lastname@example.org>
Tested-by: TYPO3com <email@example.com>
Tested-by: Benni Mack <firstname.lastname@example.org>
Reviewed-by: Benjamin Franzke <email@example.com>
Reviewed-by: Benni Mack <firstname.lastname@example.org>
#2 Updated by Gerrit Code Review 7 months ago
- Status changed from New to Under Review
Patch set 1 for branch 9.5 of project Packages/TYPO3.CMS has been pushed to the review server.
It is available at https://review.typo3.org/c/Packages/TYPO3.CMS/+/61652