rgoers commented on pull request #697:
URL: https://github.com/apache/logging-log4j2/pull/697#issuecomment-1011817999
This scares the heck out of me. 1,995 files modified means no human could
review this. Gary used to (still does?) use tools to do formatting and
invariably would change a p
garydgregory commented on pull request #697:
URL: https://github.com/apache/logging-log4j2/pull/697#issuecomment-1011749927
FWIW, in Eclipse at least you can use a customizable comment to disable the
formatted for specific areas like this:
...
// @formatter:off
...
// this
[
https://issues.apache.org/jira/browse/LOG4J2-?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ryan Schmitt updated LOG4J2-:
-
Description:
I ran into a deadlock involving {{ThreadContextDataInjector}} and the "Thread
Cont
[
https://issues.apache.org/jira/browse/LOG4J2-?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ryan Schmitt updated LOG4J2-:
-
Description:
I ran into a deadlock involving {{ThreadContextDataInjector}} and the "Thread
Cont
[
https://issues.apache.org/jira/browse/LOG4J2-3323?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17475079#comment-17475079
]
Ryan Schmitt commented on LOG4J2-3323:
--
We are now, I don't remember if it was out
Ryan Schmitt created LOG4J2-:
Summary: Classloader deadlock in ThreadContextDataInjector
Key: LOG4J2-
URL: https://issues.apache.org/jira/browse/LOG4J2-
Project: Log4j 2
Issue Typ
carterkozak opened a new pull request #697:
URL: https://github.com/apache/logging-log4j2/pull/697
_This pr is meant only as an example for discussion_
What do you think about using a code formatter? In my experience, it makes
reviews easier, avoids unnecessary style commits later on
[
https://issues.apache.org/jira/browse/LOG4J2-3323?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17475022#comment-17475022
]
Gary D. Gregory commented on LOG4J2-3323:
-
Hi [~rschmitt]
Make sure guys are o
[
https://issues.apache.org/jira/browse/LOG4J2-3323?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17474990#comment-17474990
]
Ryan Schmitt commented on LOG4J2-3323:
--
I found this upgrade while mass-upgrading m
[
https://issues.apache.org/jira/browse/LOG4J2-3323?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17474990#comment-17474990
]
Ryan Schmitt edited comment on LOG4J2-3323 at 1/12/22, 10:16 PM:
-
[
https://issues.apache.org/jira/browse/LOG4J2-3332?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ron Grabowski updated LOG4J2-3332:
--
Description:
Sending hundreds of buffered messages in an email body makes it difficult to
vie
Ron Grabowski created LOG4J2-3332:
-
Summary: SmtpAppender: add capability to send buffered messages as
an email attachment (text, zip, gzip)
Key: LOG4J2-3332
URL: https://issues.apache.org/jira/browse/LOG4J2-3332
[
https://issues.apache.org/jira/browse/LOG4J2-1192?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17474979#comment-17474979
]
Ron Grabowski commented on LOG4J2-1192:
---
Support for dynamic subject was added wit
MouettE-SC commented on pull request #682:
URL: https://github.com/apache/logging-log4j2/pull/682#issuecomment-1011391582
Let me know if there is anything I can do to help, like opening an issue on
Jira, writing the documentation part or anything, I'll be happy to !
--
This is an automat
MouettE-SC commented on pull request #682:
URL: https://github.com/apache/logging-log4j2/pull/682#issuecomment-1011384397
Sorry, forgot to comment that I was able to create working tests for the
environment arbiter using system-lambda. Hope you'll find them satisfying !
--
This is an aut
BUILD SUCCESS
Build URL
https://ci-builds.apache.org/job/Logging/job/log4j/job/release-2.x/697/
Project:
release-2.x
Date of build:
Wed, 12 Jan 2022 18:22:12 +
Build duration:
1 hr 3 min and counting
JUnit Tests
Name: (root) Failed: 0 test(s), Pa
avandeursen opened a new pull request #696:
URL: https://github.com/apache/logging-log4j2/pull/696
I noticed that the central `substitute` method in the `StrSubstitutor` class
that was involved in a recent CVE had some code not covered by (unit) tests.
This untested logic related to cases
BUILD UNSTABLE
Build URL
https://ci-builds.apache.org/job/Logging/job/log4j/job/release-2.x/696/
Project:
release-2.x
Date of build:
Wed, 12 Jan 2022 17:01:26 +
Build duration:
1 hr 2 min and counting
JUnit Tests
Name: (root) Failed: 0 test(s), P
[
https://issues.apache.org/jira/browse/LOG4J2-3331?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17474641#comment-17474641
]
Carter Kozak commented on LOG4J2-3331:
--
Does your layout implement {{LocationAware}
Ning Ning Han created LOG4J2-3331:
-
Summary: After upgrading version 2.13, the className and
lineNumber cannot be obtained
Key: LOG4J2-3331
URL: https://issues.apache.org/jira/browse/LOG4J2-3331
Proje
BUILD UNSTABLE
Build URL
https://ci-builds.apache.org/job/Logging/job/log4j/job/release-2.x/695/
Project:
release-2.x
Date of build:
Wed, 12 Jan 2022 14:03:51 +
Build duration:
1 hr 16 min and counting
JUnit Tests
Name: (root) Failed: 0 test(s),
[
https://issues.apache.org/jira/browse/LOG4J2-3330?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17474552#comment-17474552
]
ASF subversion and git services commented on LOG4J2-3330:
-
Commi
[
https://issues.apache.org/jira/browse/LOG4J2-3330?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17474551#comment-17474551
]
ASF subversion and git services commented on LOG4J2-3330:
-
Commi
[
https://issues.apache.org/jira/browse/LOG4J2-3330?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gary D. Gregory resolved LOG4J2-3330.
-
Fix Version/s: 2.17.2
Resolution: Fixed
> Configurator.setLevel not fetching the
[
https://issues.apache.org/jira/browse/LOG4J2-3330?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17474547#comment-17474547
]
ASF subversion and git services commented on LOG4J2-3330:
-
Commi
[
https://issues.apache.org/jira/browse/LOG4J2-3330?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17474546#comment-17474546
]
Gary D. Gregory commented on LOG4J2-3330:
-
[~mlemnaru]
Please try the git bran
[
https://issues.apache.org/jira/browse/LOG4J2-3330?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17474497#comment-17474497
]
Gary D. Gregory edited comment on LOG4J2-3330 at 1/12/22, 1:34 PM:
---
[
https://issues.apache.org/jira/browse/LOG4J2-3330?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17474509#comment-17474509
]
ASF subversion and git services commented on LOG4J2-3330:
-
Commi
[
https://issues.apache.org/jira/browse/LOG4J2-3330?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17474510#comment-17474510
]
ASF subversion and git services commented on LOG4J2-3330:
-
Commi
[
https://issues.apache.org/jira/browse/LOG4J2-3330?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17474497#comment-17474497
]
Gary D. Gregory commented on LOG4J2-3330:
-
The problems applies to the following
[
https://issues.apache.org/jira/browse/LOG4J2-3330?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Work on LOG4J2-3330 started by Gary D. Gregory.
---
> Configurator.setLevel not fetching the correct LoggerContext
>
[
https://issues.apache.org/jira/browse/LOG4J2-3330?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gary D. Gregory reassigned LOG4J2-3330:
---
Assignee: Gary D. Gregory
> Configurator.setLevel not fetching the correct LoggerCo
[
https://issues.apache.org/jira/browse/LOG4J2-3330?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mircea Lemnaru updated LOG4J2-3330:
---
Description:
I needed to set the log level for a certain logger in the application and for
Mircea Lemnaru created LOG4J2-3330:
--
Summary: Configurator.setLevel not fetching the correct
LoggerContext
Key: LOG4J2-3330
URL: https://issues.apache.org/jira/browse/LOG4J2-3330
Project: Log4j 2
34 matches
Mail list logo