Suvrat1629 commented on code in PR #3394:
URL: https://github.com/apache/logging-log4j2/pull/3394#discussion_r1929493785
##
log4j-core/src/main/java/org/apache/logging/log4j/core/appender/HttpAppenderBuilderTest.java:
##
@@ -0,0 +1,128 @@
+package org.apache.logging.log4j.core.a
Suvrat1629 commented on code in PR #3394:
URL: https://github.com/apache/logging-log4j2/pull/3394#discussion_r1929493785
##
log4j-core/src/main/java/org/apache/logging/log4j/core/appender/HttpAppenderBuilderTest.java:
##
@@ -0,0 +1,128 @@
+package org.apache.logging.log4j.core.a
kvssg123 commented on issue #3408:
URL:
https://github.com/apache/logging-log4j2/issues/3408#issuecomment-2613788390
Thank you for your response. We are currently using Log4j version 2.17.2.
The issue occurs exclusively in our production clusters running on AWS EKS. We
attempted to reprodu
swebb2066 opened a new pull request, #462:
URL: https://github.com/apache/logging-log4cxx/pull/462
This PR logs a warning instead of throwing an exception when the time zone
specifier is invalid.
--
This is an automated message from the Apache Git Service.
To respond to the message, pleas
swebb2066 commented on code in PR #460:
URL: https://github.com/apache/logging-log4cxx/pull/460#discussion_r1929466213
##
src/fuzzers/cpp/DOMConfiguratorFuzzer.cpp:
##
@@ -0,0 +1,37 @@
+/*
+ * Licensed to the Apache Software Foundation (ASF) under one or more
+ * contributor lic
swebb2066 commented on code in PR #460:
URL: https://github.com/apache/logging-log4cxx/pull/460#discussion_r1929430574
##
src/fuzzers/cpp/DOMConfiguratorFuzzer.cpp:
##
@@ -0,0 +1,37 @@
+/*
+ * Licensed to the Apache Software Foundation (ASF) under one or more
+ * contributor lic
rm5248 commented on code in PR #460:
URL: https://github.com/apache/logging-log4cxx/pull/460#discussion_r1929428005
##
src/fuzzers/cpp/DOMConfiguratorFuzzer.cpp:
##
@@ -0,0 +1,37 @@
+/*
+ * Licensed to the Apache Software Foundation (ASF) under one or more
+ * contributor licens
swebb2066 commented on code in PR #460:
URL: https://github.com/apache/logging-log4cxx/pull/460#discussion_r1929420033
##
src/fuzzers/cpp/DOMConfiguratorFuzzer.cpp:
##
@@ -0,0 +1,37 @@
+/*
+ * Licensed to the Apache Software Foundation (ASF) under one or more
+ * contributor lic
AdamKorcz commented on code in PR #460:
URL: https://github.com/apache/logging-log4cxx/pull/460#discussion_r1929397074
##
src/fuzzers/cpp/DOMConfiguratorFuzzer.cpp:
##
@@ -0,0 +1,37 @@
+/*
+ * Licensed to the Apache Software Foundation (ASF) under one or more
+ * contributor lic
swebb2066 commented on code in PR #460:
URL: https://github.com/apache/logging-log4cxx/pull/460#discussion_r1929382595
##
src/fuzzers/cpp/DOMConfiguratorFuzzer.cpp:
##
@@ -0,0 +1,37 @@
+/*
+ * Licensed to the Apache Software Foundation (ASF) under one or more
+ * contributor lic
swebb2066 commented on PR #456:
URL: https://github.com/apache/logging-log4cxx/pull/456#issuecomment-2613607687
Advice from [libFuzzer
documentation](https://llvm.org/docs/LibFuzzer.html#id23) is:
> Usually, the narrower the target the better. E.g. if your target can parse
several da
swebb2066 merged PR #455:
URL: https://github.com/apache/logging-log4cxx/pull/455
--
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
AdamKorcz opened a new pull request, #461:
URL: https://github.com/apache/logging-log4cxx/pull/461
Adds a fuzzer that tests `TimeBasedRollingPolicy->rollover()`.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL
[
https://issues.apache.org/jira/browse/LOG4J2-3692?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17916848#comment-17916848
]
Philippe Cloutier commented on LOG4J2-3692:
---
Thank you very much [~pkarwasz],
amosshi commented on issue #3207:
URL:
https://github.com/apache/logging-log4j2/issues/3207#issuecomment-2613344927
Hi @TiloGit ,
I have connected with
https://github.com/serilog/serilog-formatting-compact/issues/69 - since it is a
.NET library cannot used by Java application, so it
github-actions[bot] merged PR #3403:
URL: https://github.com/apache/logging-log4j2/pull/3403
--
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: notificatio
TiloGit commented on issue #3207:
URL:
https://github.com/apache/logging-log4j2/issues/3207#issuecomment-2613175262
@amosshi I really like your idea and suggestion. Did you get a chance to add
a PR to https://github.com/clef-json/clef-json.github.io?
--
This is an automated message from
ppkarwasz commented on code in PR #3394:
URL: https://github.com/apache/logging-log4j2/pull/3394#discussion_r1929043642
##
log4j-core-test/${test:logging.path}/AsyncLoggerTest.log:
##
@@ -0,0 +1,75 @@
+INFO c.f.Bar mapvalue [stackvalue] {KEY=mapvalue, configProp=configValue,
co
Suvrat1629 commented on code in PR #3394:
URL: https://github.com/apache/logging-log4j2/pull/3394#discussion_r1929040625
##
log4j-core-test/${test:logging.path}/AsyncLoggerTest.log:
##
@@ -0,0 +1,75 @@
+INFO c.f.Bar mapvalue [stackvalue] {KEY=mapvalue, configProp=configValue,
c
ppkarwasz commented on code in PR #3394:
URL: https://github.com/apache/logging-log4j2/pull/3394#discussion_r1928983602
##
log4j-core-test/${test:logging.path}/AsyncLoggerTest.log:
##
@@ -0,0 +1,75 @@
+INFO c.f.Bar mapvalue [stackvalue] {KEY=mapvalue, configProp=configValue,
co
Suvrat1629 commented on PR #3394:
URL: https://github.com/apache/logging-log4j2/pull/3394#issuecomment-2612851523
i have made the necessary fix to the code please review the code.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHu
vy commented on PR #456:
URL: https://github.com/apache/logging-log4cxx/pull/456#issuecomment-2612781932
Wouldn't it be better to only update the pattern in
`PatternLayoutFuzzer.properties` (which is employed by
`PatternLayoutFuzzer.cpp`) instead of creating a new fuzzer?
--
This is an a
vy commented on issue #3399:
URL:
https://github.com/apache/logging-log4j2/issues/3399#issuecomment-2612403140
> I am stumbling upon (probably) the same problem and can reliably reproduce
it. I could share stack traces if that helps, but sadly I cannot hand out a
minimal example because we
freelon commented on issue #3399:
URL:
https://github.com/apache/logging-log4j2/issues/3399#issuecomment-2612268508
I am stumbling upon (probably) the same problem and can reliably reproduce
it. I could share stack traces if that helps, but sadly I cannot hand out a
minimal example because
github-actions[bot] merged PR #3411:
URL: https://github.com/apache/logging-log4j2/pull/3411
--
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: notificatio
github-actions[bot] merged PR #3410:
URL: https://github.com/apache/logging-log4j2/pull/3410
--
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: notificatio
vy commented on PR #3398:
URL: https://github.com/apache/logging-log4j2/pull/3398#issuecomment-2612231112
> So you eliminated the `RecyclerFactories` static registry and reused the
type converter registry? Can you mark `RecyclerFactories` as deprecated?
Good catch. Fixed in 6f216f91cc
github-actions[bot] merged PR #319:
URL: https://github.com/apache/logging-parent/pull/319
--
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
vy commented on issue #3408:
URL:
https://github.com/apache/logging-log4j2/issues/3408#issuecomment-2612009321
1. Which Log4j version?
2. If you're not using the most recent version (i.e., `2.24.3`), do you
still observe the problem when you upgrade to `2.24.3`?
3. Do you still observ
29 matches
Mail list logo
