Activity
From 2013-05-17 to 2013-06-15
2013-06-15
-
17:02 Story #32556 (Resolved): As a developer, I'd need a documentation on how to use the Logging API
- Resolved with #39738
-
17:00 Task #32684 (Resolved): Find all core documentation which describe log severity levels
- Decision was to introduce severities according to RFC 3164 and it has been implemented in "@TYPO3\CMS\Core\Log\LegLev...
-
16:52 Bug #28481 (Rejected): sys_log insertions should not take processing time
-
16:52 Bug #28481: sys_log insertions should not take processing time
- I reject this issue, because:
1) INSERT DELAYED is deprecated. See #46616 and http://dev.mysql.com/doc/refman/5.6/... -
14:23 Bug #28481: sys_log insertions should not take processing time
- With the new Logging API, this becomes a feature of the actual writer.
A database writer cannot simply do that. Us... -
16:46 Task #46616 (Rejected): Evaluate usage of INSERT DELAYED INTO for DatabaseWriter
-
14:29 Task #46616: Evaluate usage of INSERT DELAYED INTO for DatabaseWriter
- And DELAYED has been deprecated. Using it is not recommended.
They are pushed into a separate thread to speed up o...
2013-06-08
-
14:55 Task #48881: PSR-3: Support log severities of type string
- Steffen Müller wrote:
> Suggestion for a lightweight solution:
> If the severity is a string, cast it to an integer... -
14:53 Task #48879: PSR-3: Validate reserved array key "exception" in LogRecord->data
- Steffen Müller wrote:
> PSR-3 expects the value type of \TYPO3\CMS\Core\Log\LogRecord->data['exception'] to be of PH... -
14:45 Task #48877: PSR-3: Cast log message to string
- Steffen Müller wrote:
> PSR-3 expects \TYPO3\CMS\Core\Log\Logger::log($severity, $message) to accept objects as $mes... -
14:44 Task #48876: PSR-3: throw InvalidArgumentException on undefined severity
- Steffen Müller wrote:
> PSR-3 expects \TYPO3\CMS\Core\Log\Logger::log($severity, ...) to throw an InvalidArgumentExc... -
14:39 Task #48880: Implement LoggerInterface from PSR-3
- Ernesto Baschny wrote:
> It's not a requirement to extend AbstractLogger,
I agree.
> we need simply to implem...
2013-06-05
-
15:57 Story #48874: As a developer I want a PSR-3 compatible Logging API
- I don't think we need adapter, since TYPO3\CMS\Core\Log\Logger already meets the requirements of Psr\Log\LoggerInterf...
-
15:08 Story #48874: As a developer I want a PSR-3 compatible Logging API
- In my understanding the major benefit of implementing a PSR-3 compatible interface in TYPO3 is not to "allow develope...
-
14:28 Story #48874 (Resolved): As a developer I want a PSR-3 compatible Logging API
- "PSR-3":https://github.com/php-fig/fig-standards/blob/master/accepted/PSR-3-logger-interface.md aims to set a standar...
-
15:20 Task #48880: Implement LoggerInterface from PSR-3
- It's not a requirement to extend AbstractLogger, we need simply to implement LoggerInterface one way of the other. Bu...
-
14:44 Task #48880 (Resolved): Implement LoggerInterface from PSR-3
- PSR-3 expects the \TYPO3\CMS\Core\Log\Logger to extend AbstractLogger which implements LoggerInterface. AbstractLogge...
-
14:58 Task #48881 (Resolved): PSR-3: Support log severities of type string
- PSR-3 LoggerInterface allows "mixed" data type for $severity in log($severity, ...)
It's "example implementation":ht... -
14:43 Task #48879 (Closed): PSR-3: Validate reserved array key "exception" in LogRecord->data
- PSR-3 expects the value type of \TYPO3\CMS\Core\Log\LogRecord->data['exception'] to be of PHP Exception.
Solution ... -
14:33 Task #48877 (Resolved): PSR-3: Cast log message to string
- PSR-3 expects \TYPO3\CMS\Core\Log\Logger::log($severity, $message) to accept objects as $message and cast them to str...
-
14:32 Task #48876 (Resolved): PSR-3: throw InvalidArgumentException on undefined severity
- PSR-3 expects \TYPO3\CMS\Core\Log\Logger::log($severity, ...) to throw an InvalidArgumentException when the given $se...
Also available in: Atom