Project

General

Profile

Actions

Bug #89120

closed

Loggers miss the requestId

Added by Helmut Hummel over 4 years ago. Updated over 4 years ago.

Status:
Closed
Priority:
Should have
Assignee:
-
Category:
-
Target version:
-
Start date:
2019-09-09
Due date:
% Done:

100%

Estimated time:
TYPO3 Version:
9
PHP Version:
Tags:
Complexity:
Is Regression:
Sprint Focus:

Description

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


Related issues 1 (0 open1 closed)

Related to TYPO3 Core - Task #84082: A LogRecord should not rely on global state (requestId from Bootstrap)Closed2018-02-28

Actions
Actions #1

Updated by Helmut Hummel over 4 years ago

  • Related to Task #84082: A LogRecord should not rely on global state (requestId from Bootstrap) added
Actions #2

Updated by Gerrit Code Review over 4 years 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

Actions #3

Updated by Helmut Hummel over 4 years ago

  • Status changed from Under Review to Resolved
  • % Done changed from 0 to 100
Actions #4

Updated by Benni Mack over 4 years ago

  • Status changed from Resolved to Closed
Actions

Also available in: Atom PDF