[
https://issues.apache.org/jira/browse/LOGCXX-558?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17582750#comment-17582750
]
Stephen Webb commented on LOGCXX-558:
-
Solution in https://github.com/apache/logging-
[
https://issues.apache.org/jira/browse/LOG4J2-3556?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17582745#comment-17582745
]
ASF subversion and git services commented on LOG4J2-3556:
-
Commi
[
https://issues.apache.org/jira/browse/LOG4J2-3573?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17582741#comment-17582741
]
ASF subversion and git services commented on LOG4J2-3573:
-
Commi
[
https://issues.apache.org/jira/browse/LOG4J2-3577?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17582742#comment-17582742
]
ASF subversion and git services commented on LOG4J2-3577:
-
Commi
[
https://issues.apache.org/jira/browse/LOG4J2-3556?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17582743#comment-17582743
]
ASF subversion and git services commented on LOG4J2-3556:
-
Commi
[
https://issues.apache.org/jira/browse/LOG4J2-3573?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17582740#comment-17582740
]
ASF subversion and git services commented on LOG4J2-3573:
-
Commi
vy merged PR #1002:
URL: https://github.com/apache/logging-log4j2/pull/1002
--
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: notifications-unsubscr...@lo
[
https://issues.apache.org/jira/browse/LOG4J2-3556?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Volkan Yazici closed LOG4J2-3556.
-
Resolution: Fixed
> JsonTemplateLayout truncation ignores exception cause
>
[
https://issues.apache.org/jira/browse/LOG4J2-3556?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Volkan Yazici updated LOG4J2-3556:
--
Fix Version/s: 2.19.0
> JsonTemplateLayout truncation ignores exception cause
> --
[
https://issues.apache.org/jira/browse/LOG4J2-3580?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17582663#comment-17582663
]
Ralph Goers commented on LOG4J2-3580:
-
Well, NoClassDefFoundError means that the org
ppkarwasz opened a new pull request, #1008:
URL: https://github.com/apache/logging-log4j2/pull/1008
When running with a security manager, `ServiceLoaderUtil` will call
`ServiceLoader` with the privileges of the caller.
This probably requires further testing to be sure it works with bo
FreeAndNil commented on PR #91:
URL: https://github.com/apache/logging-log4net/pull/91#issuecomment-1221592232
No problem. In the meantime I can release a version to our internal Nuget
repo.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log
fluffynuts commented on PR #91:
URL: https://github.com/apache/logging-log4net/pull/91#issuecomment-1221585721
I'm not sure when this will land in a release; I'd like to work around an
issue introduced recently which fixes something for pqsql but potentially
breaks something for mssql (tho
shamim created LOG4J2-3580:
--
Summary: issue while using log4j version 2.17.2
Key: LOG4J2-3580
URL: https://issues.apache.org/jira/browse/LOG4J2-3580
Project: Log4j 2
Issue Type: Bug
Rep
FreeAndNil commented on PR #91:
URL: https://github.com/apache/logging-log4net/pull/91#issuecomment-1221555904
Thank you very much.
--
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 co
fluffynuts merged PR #92:
URL: https://github.com/apache/logging-log4net/pull/92
--
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: notifications-unsubscr.
fluffynuts merged PR #91:
URL: https://github.com/apache/logging-log4net/pull/91
--
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: notifications-unsubscr.
fluffynuts merged PR #93:
URL: https://github.com/apache/logging-log4net/pull/93
--
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: notifications-unsubscr.
ppkarwasz commented on PR #1006:
URL: https://github.com/apache/logging-log4j2/pull/1006#issuecomment-1221536060
@boris-unckel, I totally share your concerns about the usage of
`AccessController.doPrivileged`, but I am not sure if #1007 solves them.
If we were to introduce additional
boris-unckel commented on PR #1006:
URL: https://github.com/apache/logging-log4j2/pull/1006#issuecomment-1221529876
@ppkarwasz I have prepared a caller based solution:
https://github.com/apache/logging-log4j2/pull/1007 I think it's better to avoid
a general purpose privileged execution util
boris-unckel opened a new pull request, #1007:
URL: https://github.com/apache/logging-log4j2/pull/1007
Add privileged actions on caller side
Fixes https://issues.apache.org/jira/browse/LOG4J2-3579
--
This is an automated message from the Apache Git Service.
To respond to the message
boris-unckel commented on PR #1006:
URL: https://github.com/apache/logging-log4j2/pull/1006#issuecomment-1221502184
@ppkarwasz
> Since `AccessController#doPrivileged` is another caller sensitive method,
I think that your PR should do the same and call it through
`MethodHandles.Looku
swebb2066 opened a new pull request, #117:
URL: https://github.com/apache/logging-log4cxx/pull/117
This commit is progrees toward resolving
[LOGCXX-558](https://issues.apache.org/jira/browse/LOGCXX-558)
--
This is an automated message from the Apache Git Service.
To respond to the messag
23 matches
Mail list logo
