coldtobi commented on pull request #79:
URL: https://github.com/apache/logging-log4cxx/pull/79#issuecomment-997165526
@ams-tschoening do you want to take another look or did I miss an open
point? (dead lock avoidance)
--
This is an automated message from the Apache Git Service.
To respon
coldtobi edited a comment on pull request #81:
URL: https://github.com/apache/logging-log4cxx/pull/81#issuecomment-997165067
> I've made a new PR with the changes, if you are able to review that would
be helpful: #85
#85 works for me; I guess then lets close this PR, as #85 replaces
coldtobi edited a comment on pull request #81:
URL: https://github.com/apache/logging-log4cxx/pull/81#issuecomment-997165067
> I've made a new PR with the changes, if you are able to review that would
be helpful: #85
#85 works for me; I guess then lets close this PR, as #85 replaces
coldtobi commented on pull request #81:
URL: https://github.com/apache/logging-log4cxx/pull/81#issuecomment-997165067
> I've made a new PR with the changes, if you are able to review that would
be helpful: #85
#85 works for me; I guess then lets close this PR, as #85 succeeds it.
-
coldtobi closed pull request #81:
URL: https://github.com/apache/logging-log4cxx/pull/81
--
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: notificat
coldtobi edited a comment on pull request #85:
URL: https://github.com/apache/logging-log4cxx/pull/85#issuecomment-997162275
LGTM! (Tested for my Debian packaging, this should solve my problems I had
there.)
--
This is an automated message from the Apache Git Service.
To respond to the m
coldtobi edited a comment on pull request #85:
URL: https://github.com/apache/logging-log4cxx/pull/85#issuecomment-997162275
LGTM! (Tested for my Debian packaging, this should solve the problems I saw
there.)
--
This is an automated message from the Apache Git Service.
To respond to the
coldtobi edited a comment on pull request #85:
URL: https://github.com/apache/logging-log4cxx/pull/85#issuecomment-997162275
LGTM!
--
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
coldtobi commented on pull request #85:
URL: https://github.com/apache/logging-log4cxx/pull/85#issuecomment-997162275
LGTM
--
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.
[
https://issues.apache.org/jira/browse/LOG4J2-3256?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17461793#comment-17461793
]
Dongjin Lee commented on LOG4J2-3256:
-
[https://github.com/apache/logging-log4j2/pul
[
https://issues.apache.org/jira/browse/LOG4J2-3256?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17461792#comment-17461792
]
Remko Popma commented on LOG4J2-3256:
-
That makes sense.
Can you provide a PR to mak
Dongjin Lee created LOG4J2-3256:
---
Summary: Reduce ignored package scope of KafkaAppender
Key: LOG4J2-3256
URL: https://issues.apache.org/jira/browse/LOG4J2-3256
Project: Log4j 2
Issue Type: Imp
BUILD UNSTABLE
Build URL
https://ci-builds.apache.org/job/Logging/job/log4j/job/release-2.x/497/
Project:
release-2.x
Date of build:
Sat, 18 Dec 2021 03:23:45 +
Build duration:
1 hr 0 min and counting
JUnit Tests
Name: (root) Failed: 0 test(s), P
rm5248 commented on pull request #81:
URL: https://github.com/apache/logging-log4cxx/pull/81#issuecomment-997136517
I've made a new PR with the changes, if you are able to review that would be
helpful: https://github.com/apache/logging-log4cxx/pull/85
--
This is an automated message from
remkop commented on pull request #639:
URL: https://github.com/apache/logging-log4j2/pull/639#issuecomment-997132387
Merged. Will be included in the next Log4j2 release.
Thank you for the contribution!
--
This is an automated message from the Apache Git Service.
To respond to the messa
[
https://issues.apache.org/jira/browse/LOG4J2-3239?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17461762#comment-17461762
]
Richard Gomez commented on LOG4J2-3239:
---
I noticed this as well. The timestamps ar
[
https://issues.apache.org/jira/browse/LOG4J2-3230?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Carter Kozak resolved LOG4J2-3230.
--
Resolution: Fixed
> Certain strings can cause infinite recursion
> ---
garydgregory merged pull request #639:
URL: https://github.com/apache/logging-log4j2/pull/639
--
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: noti
[
https://issues.apache.org/jira/browse/LOG4J2-3254?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17461725#comment-17461725
]
Remko Popma commented on LOG4J2-3254:
-
Thank you for raising this.
I have started t
remkop removed a comment on pull request #630:
URL: https://github.com/apache/logging-log4j2/pull/630#issuecomment-997062659
Thank you for your analysis and writeup.
I can understand how there can be potential confusion between a call to
`logger.debug(String)`, `logger.debug(Object)`
remkop edited a comment on pull request #630:
URL: https://github.com/apache/logging-log4j2/pull/630#issuecomment-997062659
Thank you for your analysis and writeup.
I can understand how there can be potential confusion between a call to
`logger.debug(String)`, `logger.debug(Object)`
remkop edited a comment on pull request #630:
URL: https://github.com/apache/logging-log4j2/pull/630#issuecomment-997062659
Thank you for your analysis and writeup.
I can understand how there can be potential confusion between a call to
`logger.debug(String)`, `logger.debug(Object)`
remkop edited a comment on pull request #630:
URL: https://github.com/apache/logging-log4j2/pull/630#issuecomment-997062659
Thank you for your analysis and writeup.
I can understand how there can be potential confusion between a call to
`logger.debug(String)`, `logger.debug(Object)`
remkop commented on pull request #630:
URL: https://github.com/apache/logging-log4j2/pull/630#issuecomment-997062659
Thank you for your analysis and writeup.
I can understand how there can be potential confusion between a call to
`logger.debug(String)`, `logger.debug(Object)` and `lo
[
https://issues.apache.org/jira/browse/LOG4J2-3230?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17461685#comment-17461685
]
Bernd Eckenfels edited comment on LOG4J2-3230 at 12/17/21, 10:13 PM:
-
[
https://issues.apache.org/jira/browse/LOG4J2-3230?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17461685#comment-17461685
]
Bernd Eckenfels commented on LOG4J2-3230:
-
Jon, I don’t think I understand the f
BUILD SUCCESS
Build URL
https://ci-builds.apache.org/job/Logging/job/log4j/job/release-2.x/490/
Project:
release-2.x
Date of build:
Fri, 17 Dec 2021 20:48:46 +
Build duration:
1 hr 10 min and counting
JUnit Tests
Name: (root) Failed: 0 test(s), P
[
https://issues.apache.org/jira/browse/LOG4J2-3253?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gary D. Gregory deleted LOG4J2-3253:
> demo
>
>
> Key: LOG4J2-3253
> URL: https://issues.apac
[
https://issues.apache.org/jira/browse/LOG4J2-3242?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17461664#comment-17461664
]
ASF subversion and git services commented on LOG4J2-3242:
-
Commi
[
https://issues.apache.org/jira/browse/LOG4J2-3237?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gary D. Gregory updated LOG4J2-3237:
Summary: Log4j 1.2 bridge API hard codes the Syslog protocol to TCP (was:
Log4j 1.2 bridg
[
https://issues.apache.org/jira/browse/LOG4J2-3230?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17461613#comment-17461613
]
Jon Bristow commented on LOG4J2-3230:
-
[~mfriedenhagen] While my initial impressions
[
https://issues.apache.org/jira/browse/LOG4J2-3230?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17461598#comment-17461598
]
Mirko Friedenhagen commented on LOG4J2-3230:
Many thanks for the clarificati
[
https://issues.apache.org/jira/browse/LOG4J2-3230?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17461563#comment-17461563
]
Jon Bristow commented on LOG4J2-3230:
-
[~mfriedenhagen]
The wacky patternLayout for
[
https://issues.apache.org/jira/browse/LOG4J2-3230?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17461546#comment-17461546
]
Matt Sicker commented on LOG4J2-3230:
-
Discussions and proposals for CVEs should be
Kranti Vikram created LOG4J2-3255:
-
Summary: Performance Benchmarking shows 20% degradation in
FileAppenderBenchmark.log4j2file between Log4j2 v2.12.0 & v2.16.0
Key: LOG4J2-3255
URL: https://issues.apache.org/ji
[
https://issues.apache.org/jira/browse/LOG4J2-3230?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17461519#comment-17461519
]
Bernd Eckenfels commented on LOG4J2-3230:
-
Do you plan a CVE for it? Unfortunate
[
https://issues.apache.org/jira/browse/LOG4J2-3254?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Marco Tenti updated LOG4J2-3254:
Description:
After the big security issue discovered with log4j2 , we need to update all the
"old
[
https://issues.apache.org/jira/browse/LOG4J2-2986?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ron Grabowski updated LOG4J2-2986:
--
Reporter: Ron Grabowski (was: Volkan Yazici)
> Allow stacktrace pattern converters to specify
[
https://issues.apache.org/jira/browse/LOG4J2-2986?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ron Grabowski updated LOG4J2-2986:
--
Reporter: Volkan Yazici (was: Ron Grabowski)
> Allow stacktrace pattern converters to specify
[
https://issues.apache.org/jira/browse/LOG4J2-2986?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ron Grabowski reassigned LOG4J2-2986:
-
Assignee: (was: Ron Grabowski)
> Allow stacktrace pattern converters to specify a s
[
https://issues.apache.org/jira/browse/LOG4J2-2986?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ron Grabowski reassigned LOG4J2-2986:
-
Assignee: (was: Ron Grabowski)
> Allow stacktrace pattern converters to specify a s
[
https://issues.apache.org/jira/browse/LOG4J2-2986?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ron Grabowski reassigned LOG4J2-2986:
-
Assignee: Ron Grabowski
> Allow stacktrace pattern converters to specify a starting poi
[
https://issues.apache.org/jira/browse/LOG4J2-3254?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Marco Tenti updated LOG4J2-3254:
Description:
After the big security issue discovered with log4j2 , we need to update all the
"old
Marco Tenti created LOG4J2-3254:
---
Summary: Need a log4j-core version 2.16 osgi compatible
Key: LOG4J2-3254
URL: https://issues.apache.org/jira/browse/LOG4J2-3254
Project: Log4j 2
Issue Type: Im
michael-buerkle opened a new pull request #639:
URL: https://github.com/apache/logging-log4j2/pull/639
According to
https://logging.apache.org/log4j/2.x/log4j-core/apidocs/org/apache/logging/log4j/core/appender/rolling/action/Duration.html#parseCharSequence
a Duration looks like "P2D"
michael-buerkle closed pull request #636:
URL: https://github.com/apache/logging-log4j2/pull/636
--
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: n
michael-buerkle commented on pull request #636:
URL: https://github.com/apache/logging-log4j2/pull/636#issuecomment-996721500
@garydgregory: Thank you for that hint.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
qxo commented on pull request #638:
URL: https://github.com/apache/logging-log4j2/pull/638#issuecomment-996713347
> Thank you for the proposal, I am handling this in a different way for
2.17.0.
ok:)
--
This is an automated message from the Apache Git Service.
To respond to the mes
qxo opened a new pull request #638:
URL: https://github.com/apache/logging-log4j2/pull/638
recursive substitute suck, we can switch it off in the
log4j2.component.properties:
```
log4j2.enableSubstitutionInVariables=false
```
--
This is an automated message from the Apache Git S
garydgregory commented on pull request #636:
URL: https://github.com/apache/logging-log4j2/pull/636#issuecomment-996675898
FYI: The current documentation is in the branch release-2.x
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to G
[
https://issues.apache.org/jira/browse/LOG4J2-3253?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17461400#comment-17461400
]
Marton commented on LOG4J2-3253:
sorry, please delete me!
> demo
>
>
>
[
https://issues.apache.org/jira/browse/LOG4J2-3253?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Marton closed LOG4J2-3253.
--
Resolution: Fixed
> demo
>
>
> Key: LOG4J2-3253
> URL: https://issues.apa
Marton created LOG4J2-3253:
--
Summary: demo
Key: LOG4J2-3253
URL: https://issues.apache.org/jira/browse/LOG4J2-3253
Project: Log4j 2
Issue Type: Bug
Affects Versions: 2.16.0
Reporter:
[
https://issues.apache.org/jira/browse/LOG4J2-3230?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17461333#comment-17461333
]
Alexander Yastrebov edited comment on LOG4J2-3230 at 12/17/21, 12:07 PM:
-
garydgregory merged pull request #635:
URL: https://github.com/apache/logging-log4j2/pull/635
--
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: noti
qxo opened a new pull request #637:
URL: https://github.com/apache/logging-log4j2/pull/637
so we can change the load order if we need:
such as lock some properties for force disable some feature we don't need.
ie:
SystemPropertiesPropertySource is priority=100, if we wan
[
https://issues.apache.org/jira/browse/LOG4J2-3230?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17461377#comment-17461377
]
Mirko Friedenhagen edited comment on LOG4J2-3230 at 12/17/21, 11:32 AM:
--
[
https://issues.apache.org/jira/browse/LOG4J2-3230?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17461377#comment-17461377
]
Mirko Friedenhagen commented on LOG4J2-3230:
So, OK with log4j-core 2.8 you
[
https://issues.apache.org/jira/browse/LOG4J2-3230?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17461376#comment-17461376
]
Mirko Friedenhagen commented on LOG4J2-3230:
Sorry folks, I just downloaded
[
https://issues.apache.org/jira/browse/LOG4J2-3230?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17461333#comment-17461333
]
Alexander Yastrebov commented on LOG4J2-3230:
-
There is an `enableSubstituti
michael-buerkle opened a new pull request #636:
URL: https://github.com/apache/logging-log4j2/pull/636
According to
https://logging.apache.org/log4j/2.x/log4j-core/apidocs/org/apache/logging/log4j/core/appender/rolling/action/Duration.html#parseCharSequence
a Duration looks like "P2D"
Arunkumar K created LOG4J2-3252:
---
Summary: Not able to implement FileAppender in log4j2 with layout
Key: LOG4J2-3252
URL: https://issues.apache.org/jira/browse/LOG4J2-3252
Project: Log4j 2
Issu
Sankalp created LOG4J2-3251:
---
Summary: Weblookup is not working if old loggercontext is removed
and tried to initialize loggerContext using Configurator.initialize
Key: LOG4J2-3251
URL: https://issues.apache.org/jira/br
mikaello opened a new pull request #14:
URL: https://github.com/apache/logging-log4j-kotlin/pull/14
I am using this library in my application, but it prevents me from upgrading
to Kotlin v1.4 since this library includes Kotlin v1.3.72. I can force my
application to use Kotlin stdlib 1.3, b
rocketraman commented on pull request #14:
URL:
https://github.com/apache/logging-log4j-kotlin/pull/14#issuecomment-996528405
Now that 1.6 is out, its time to resurrect this and move to 1.4.
--
This is an automated message from the Apache Git Service.
To respond to the message, please lo
65 matches
Mail list logo
