srdo commented on pull request #644:
URL: https://github.com/apache/logging-log4j2/pull/644#issuecomment-997681581
@quaff I don't think that fixes the same thing? This fix is trying to limit
recursion depth in all cases, the fix you are linking disables recursion in
some cases.
--
This
[
https://issues.apache.org/jira/browse/LOGCXX-544?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17462427#comment-17462427
]
Tobias Frost commented on LOGCXX-544:
-
Yeah, PR #76 will help.
For the build failure
quaff commented on pull request #617:
URL: https://github.com/apache/logging-log4j2/pull/617#issuecomment-997667402
@rgoers , Please take a look at this.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above t
quaff commented on pull request #644:
URL: https://github.com/apache/logging-log4j2/pull/644#issuecomment-997665780
@srdo , I think your PR should be closed, `isRecursiveEvaluationAllowed()`
is introduced by
https://github.com/apache/logging-log4j2/commit/806023265f8c905b2dd1d81fd2458f64b2
[
https://issues.apache.org/jira/browse/LOG4J2-3258?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Konstantinos Liakos updated LOG4J2-3258:
Description:
A configuration like the below has stopped working since 2.17.0. The
[
https://issues.apache.org/jira/browse/LOG4J2-3258?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Konstantinos Liakos updated LOG4J2-3258:
Description:
A configuration like the below has stopped working since 2.17.0. The
[
https://issues.apache.org/jira/browse/LOG4J2-3260?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Abhishek Arya updated LOG4J2-3260:
--
Description:
The branch protection setting is missing on
[https://github.com/apache/logging-l
[
https://issues.apache.org/jira/browse/LOG4J2-3258?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17462413#comment-17462413
]
Konstantinos Liakos commented on LOG4J2-3258:
-
Hi [~rgoers] , please find be
[
https://issues.apache.org/jira/browse/LOG4J2-3258?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17462413#comment-17462413
]
Konstantinos Liakos edited comment on LOG4J2-3258 at 12/20/21, 7:00 AM:
--
[
https://issues.apache.org/jira/browse/LOG4J2-3260?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Abhishek Arya updated LOG4J2-3260:
--
Description:
Please check
[https://github.com/ossf/scorecard/blob/090ae4f0bbc3b6956971bec8353
[
https://issues.apache.org/jira/browse/LOG4J2-3260?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Abhishek Arya updated LOG4J2-3260:
--
Description:
Please check
[https://github.com/ossf/scorecard/blob/090ae4f0bbc3b6956971bec8353
Abhishek Arya created LOG4J2-3260:
-
Summary: Missing branch protection settings on log4j2 repo
Key: LOG4J2-3260
URL: https://issues.apache.org/jira/browse/LOG4J2-3260
Project: Log4j 2
Issue T
[
https://issues.apache.org/jira/browse/LOG4J2-3198?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17462404#comment-17462404
]
ASF subversion and git services commented on LOG4J2-3198:
-
Commi
[
https://issues.apache.org/jira/browse/LOG4J2-3242?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17462359#comment-17462359
]
ASF subversion and git services commented on LOG4J2-3242:
-
Commi
remkop commented on pull request #608:
URL: https://github.com/apache/logging-log4j2/pull/608#issuecomment-997537941
@quaff Thanks for noticing this!
The Log4j [security
page](https://logging.apache.org/log4j/2.x/security.html) has already been
updated to reflect this.
I believe
quaff commented on pull request #608:
URL: https://github.com/apache/logging-log4j2/pull/608#issuecomment-997530030
> @remkop Description of `CVE-2021-45046` is not accurate, could you verify
and update security page?
>
> > Thread Context Map pattern (%X, %mdc, or %MDC)
>
> I
[
https://issues.apache.org/jira/browse/LOG4J2-3250?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17462348#comment-17462348
]
Yanming Zhou commented on LOG4J2-3250:
--
Confirm fixed in 2.17.0, please close it.
[
https://issues.apache.org/jira/browse/LOG4J2-3250?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Yanming Zhou closed LOG4J2-3250.
Resolution: Fixed
> Consider remove recursive replace for lookups
> --
[
https://issues.apache.org/jira/browse/LOG4J2-3250?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Yanming Zhou updated LOG4J2-3250:
-
Fix Version/s: 2.17.0
> Consider remove recursive replace for lookups
>
[
https://issues.apache.org/jira/browse/LOG4J2-2819?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Remko Popma updated LOG4J2-2819:
Fix Version/s: 2.12.3
> Add support for specifying an SSL configuration for SmtpAppender
> ---
[
https://issues.apache.org/jira/browse/LOG4J2-3242?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17462337#comment-17462337
]
ASF subversion and git services commented on LOG4J2-3242:
-
Commi
[
https://issues.apache.org/jira/browse/LOG4J2-3258?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17462333#comment-17462333
]
Ralph Goers commented on LOG4J2-3258:
-
I'm misunderstanding something. You say that
[
https://issues.apache.org/jira/browse/LOG4J2-3258?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17462333#comment-17462333
]
Ralph Goers edited comment on LOG4J2-3258 at 12/19/21, 10:54 PM:
-
[
https://issues.apache.org/jira/browse/LOG4J2-3257?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17462311#comment-17462311
]
Ralph Goers commented on LOG4J2-3257:
-
Yeah, your exception is telling you that the
srdo commented on pull request #644:
URL: https://github.com/apache/logging-log4j2/pull/644#issuecomment-997469084
Sorry, I should have asked more clearly. What I meant was "How are you
ensuring that this fix will also be applied to master, is it by cherry-pick or
by merging 2.x into maste
garydgregory edited a comment on pull request #644:
URL: https://github.com/apache/logging-log4j2/pull/644#issuecomment-997464275
> @garydgregory Thanks, will close this and move it to another branch. I
assume you cherry-pick/merge forward on this project then?
Yes, just a plain merg
garydgregory edited a comment on pull request #644:
URL: https://github.com/apache/logging-log4j2/pull/644#issuecomment-997464275
> @garydgregory Thanks, will close this and move it to another branch. I
assume you cherry-pick/merge forward on this project then?
Yes, just a plain merg
garydgregory commented on pull request #644:
URL: https://github.com/apache/logging-log4j2/pull/644#issuecomment-997464275
> @garydgregory Thanks, will close this and move it to another branch. I
assume you cherry-pick/merge forward on this project then?
No, just a plain merge from G
srdo commented on pull request #644:
URL: https://github.com/apache/logging-log4j2/pull/644#issuecomment-997462128
@garydgregory Thanks, will close this and move it to another branch. I
assume you cherry-pick/merge forward on this project then?
--
This is an automated message from the Ap
srdo closed pull request #644:
URL: https://github.com/apache/logging-log4j2/pull/644
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: notification
garydgregory commented on pull request #644:
URL: https://github.com/apache/logging-log4j2/pull/644#issuecomment-997461971
Hi @srdo
Wrong branch: You want to target `release-2.x`.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to
srdo commented on pull request #644:
URL: https://github.com/apache/logging-log4j2/pull/644#issuecomment-997461040
Jira https://issues.apache.org/jira/browse/LOG4J2-3259
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use
srdo opened a new pull request #644:
URL: https://github.com/apache/logging-log4j2/pull/644
I've hard coded the limit to 10. If you feel the limit needs to be
configurable (via system property or the log4j config?), let me know and I'll
adjust.
I couldn't find a good way to keep the
Stig Rohde Døssing created LOG4J2-3259:
--
Summary: Limit string interpolation recursion level.
Key: LOG4J2-3259
URL: https://issues.apache.org/jira/browse/LOG4J2-3259
Project: Log4j 2
Iss
dpsenner opened a new pull request #643:
URL: https://github.com/apache/logging-log4j2/pull/643
This PR adds a sentence that explains users what to do before posting
messages to a mailing list.
--
This is an automated message from the Apache Git Service.
To respond to the message, please
Konstantinos Liakos created LOG4J2-3258:
---
Summary: RollingFile fileName containing variables does not work
on 2.17.0
Key: LOG4J2-3258
URL: https://issues.apache.org/jira/browse/LOG4J2-3258
Proje
[
https://issues.apache.org/jira/browse/LOG4J2-3257?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=1746#comment-1746
]
Mike commented on LOG4J2-3257:
--
I can certainly look - however, I've upgraded to 15, then 1
[
https://issues.apache.org/jira/browse/LOG4J2-3257?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17462218#comment-17462218
]
Gary D. Gregory commented on LOG4J2-3257:
-
This class has not changed its API si
[
https://issues.apache.org/jira/browse/LOG4J2-3257?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mike updated LOG4J2-3257:
-
Description:
We use MDC.put for a variety of things. With the 2.17 version, it appears
there is a bug.
When i
[
https://issues.apache.org/jira/browse/LOG4J2-3257?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mike updated LOG4J2-3257:
-
Description:
We use MDC.put for a variety of things. With the 2.17 version it appears there
is a bug.
When in
Mike created LOG4J2-3257:
Summary: MDC class in 2.17.0 has multiple "put" methods
Key: LOG4J2-3257
URL: https://issues.apache.org/jira/browse/LOG4J2-3257
Project: Log4j 2
Issue Type: Bug
Co
Sadboipoor commented on a change in pull request #75:
URL: https://github.com/apache/logging-log4cxx/pull/75#discussion_r771956556
##
File path: src/main/cpp/locationinfo.cpp
##
@@ -102,6 +120,14 @@ const char* LocationInfo::getFileName() const
return fileName;
}
+/*
Sadboipoor commented on pull request #82:
URL: https://github.com/apache/logging-log4cxx/pull/82#issuecomment-997399720
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To u
KristjanESPERANTO opened a new pull request #642:
URL: https://github.com/apache/logging-log4j2/pull/642
It's a minor detail, but I didn't find any reference to the release history
in the repository.
--
This is an automated message from the Apache Git Service.
To respond to the message,
44 matches
Mail list logo
