[
https://issues.apache.org/jira/browse/LOG4J2-3627?focusedWorklogId=924241&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-924241
]
ASF GitHub Bot logged work on LOG4J2-3627:
------------------------------------------
Author: ASF GitHub Bot
Created on: 02/Jul/24 17:06
Start Date: 02/Jul/24 17:06
Worklog Time Spent: 10m
Work Description: ppkarwasz commented on PR #2691:
URL: https://github.com/apache/logging-log4j2/pull/2691#issuecomment-2197939455
Note about the test failures: unfortunately we have about a dozen of flaky
tests in our project (see the [Develocity
statistics](https://ge.apache.org/scans/tests?search.rootProjectNames=*log4j*&search.timeZoneId=UTC#)
for a list).
The failures in those tests are not specific to this PR.
The failures in the Log4j Tag Library on the other hand seem connected to
this PR and need to be investigated.
Issue Time Tracking
-------------------
Worklog Id: (was: 924241)
Time Spent: 2h 10m (was: 2h)
> PatternLayout: %xEx{ [ "short" | depth]} not working
> ----------------------------------------------------
>
> Key: LOG4J2-3627
> URL: https://issues.apache.org/jira/browse/LOG4J2-3627
> Project: Log4j 2
> Issue Type: Bug
> Components: Layouts
> Affects Versions: 2.11.0, 2.11.1, 2.11.2, 2.12.0, 2.12.1, 2.13.0, 2.13.1,
> 2.13.2, 2.14.0, 2.13.3, 2.14.1, 2.15.0, 2.16.0, 2.17.1, 2.17.0, 2.12.3,
> 2.12.2, 2.18.0, 2.12.4, 2.17.2, 2.19.0
> Reporter: Thorsten Heit
> Assignee: Volkan Yazici
> Priority: Minor
> Time Spent: 2h 10m
> Remaining Estimate: 0h
>
> According to the documentation the patterns {{{}%xEx{short{}}}} or
> {{{}%xEx{<num>{}}}} should limit the number of lines of a stack trace that is
> logged. This doesn't work; instead, the complete stack trace is logged
> (always!). This is in contrary to the patterns {{%ex}} or {{%rEx}} where this
> works.
> In commit 9ff63b2e50be754ae394feda2c33d9e64fd0ab3a (2018-01-25) a change was
> implemented because of LOG4J2-2195 (according to the commit message) that
> removed the option of limiting the number of lines to output.
> Therefore all versions since 2.11.0 should be affected.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
