SwEngine commented on issue #142:
URL:
https://github.com/apache/logging-log4net/issues/142#issuecomment-2076426672
I am on vacation, but next week I will look at again, thank you so much!
--
This is an automated message from the Apache Git Service.
To respond to the message, please log
ppkarwasz commented on PR #2515:
URL: https://github.com/apache/logging-log4j2/pull/2515#issuecomment-2076300336
I don't think additional tests are needed, since your changes should be
covered by the current ones.
Please add a changelog entry.
--
This is an automated message from t
swebb2066 merged PR #371:
URL: https://github.com/apache/logging-log4cxx/pull/371
--
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
PassiveIncomeMachine opened a new issue, #2516:
URL: https://github.com/apache/logging-log4j2/issues/2516
## Constructor ERROR Could not create plugin of type class
org.apache.logging.log4j.layout.template.json.JsonTemplateLayout for element
JsonTemplateLayout: java.lang.OutOfMemoryError: J
[
https://issues.apache.org/jira/browse/LOG4J2-3455?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Piotr Karwasz resolved LOG4J2-3455.
---
Resolution: Information Provided
> Log4j 1.x 2.17.2 bridge - Thread specific Log Level Thres
michaelbraun commented on PR #2515:
URL: https://github.com/apache/logging-log4j2/pull/2515#issuecomment-2075884028
> @michaelbraun,
>
> Looks good to me. Thank you for your contribution.
Does this change need a file in the changelog or additional tests before
merging?
--
T
michaelbraun opened a new pull request, #2515:
URL: https://github.com/apache/logging-log4j2/pull/2515
In a few places in code, DateTimeFormatter.format(...) is called on an
Instant, which creates a new String, when this is just appended to a
StringBuilder. This can be improved by calling D
ppkarwasz merged PR #2500:
URL: https://github.com/apache/logging-log4j2/pull/2500
--
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-unsubsc
vy opened a new issue, #2508:
URL: https://github.com/apache/logging-log4j2/issues/2508
As agreed in [the site structure
document](https://docs.google.com/document/d/10Fu7oqDzdM_D6LbexzwX9arh51Tic7AGvkWTQrL6jjQ/edit),
create a `concepts.adoc` such that:
- Title: _"Log4j, SLF4J, JUL,
vy opened a new issue, #2507:
URL: https://github.com/apache/logging-log4j2/issues/2507
As agreed in [the site structure
document](https://docs.google.com/document/d/10Fu7oqDzdM_D6LbexzwX9arh51Tic7AGvkWTQrL6jjQ/edit),
create a _"Log4j in under 2 minutes!"_ page with following goals in mind:
vy opened a new issue, #2506:
URL: https://github.com/apache/logging-log4j2/issues/2506
As agreed in [the site structure
document](https://docs.google.com/document/d/10Fu7oqDzdM_D6LbexzwX9arh51Tic7AGvkWTQrL6jjQ/edit),
revamp `faq.adoc` with following goals in mind:
- Rework the exist
github-actions[bot] merged PR #2502:
URL: https://github.com/apache/logging-log4j2/pull/2502
--
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 code in PR #2505:
URL: https://github.com/apache/logging-log4j2/pull/2505#discussion_r1577848392
##
log4j-core/src/main/java/org/apache/logging/log4j/core/Logger.java:
##
@@ -63,16 +77,82 @@ public class Logger extends AbstractLogger implements
Supplier {
p
swebb2066 closed issue #370: Use Logging Services common pages
URL: https://github.com/apache/logging-log4cxx/issues/370
--
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 unsu
vy commented on code in PR #2500:
URL: https://github.com/apache/logging-log4j2/pull/2500#discussion_r1577748113
##
.github/workflows/close-stale.yaml:
##
@@ -0,0 +1,39 @@
+#
+# Licensed to the Apache Software Foundation (ASF) under one or more
+# contributor license agreements.
ppkarwasz commented on code in PR #2505:
URL: https://github.com/apache/logging-log4j2/pull/2505#discussion_r1577750867
##
log4j-core/src/main/java/org/apache/logging/log4j/core/Logger.java:
##
@@ -63,16 +77,82 @@ public class Logger extends AbstractLogger implements
Supplier {
ppkarwasz commented on PR #2500:
URL: https://github.com/apache/logging-log4j2/pull/2500#issuecomment-2074727316
@vy,
I added a second workflow that adds a `waiting-for-maintainer` label and
removes `waiting-for-user` whenever:
* an issue is created,
* a user comments on an
github-actions[bot] merged PR #2504:
URL: https://github.com/apache/logging-log4j2/pull/2504
--
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 #72:
URL: https://github.com/apache/logging-log4j-kotlin/pull/72
--
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
vy commented on issue #370:
URL:
https://github.com/apache/logging-log4cxx/issues/370#issuecomment-2074403480
> Adding Log4cxx and Log4Net to the coverage makes it hard to write user
specific text.
For the record, this statement is not completely correct; Log4Net is already
using th
vy commented on issue #370:
URL:
https://github.com/apache/logging-log4cxx/issues/370#issuecomment-2074399373
@swebb2066, [I offered you to close this ticket if you think Log4cxx is
doing
fine](https://github.com/apache/logging-log4cxx/issues/370#issuecomment-2071664759):
> If, as t
swebb2066 commented on issue #370:
URL:
https://github.com/apache/logging-log4cxx/issues/370#issuecomment-2074336080
> Please feel free to make changes as see fit
I am not convinced generalised documentation is good documentation so I
would not be able to help.
> Log4cxx has o
vy closed issue #2414: `PropertiesUtil` fails due to blank key lookup
URL: https://github.com/apache/logging-log4j2/issues/2414
--
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.
vy commented on issue #370:
URL:
https://github.com/apache/logging-log4cxx/issues/370#issuecomment-2074228484
> > Pages I cited are implemented in a project agnostic way.
>
> They really do not read like that. They are heavily oriented towards Log4j.
Please feel free to make ch
24 matches
Mail list logo
