wrohv commented on issue #425:
URL:
https://github.com/apache/logging-log4cxx/issues/425#issuecomment-2460981177
I tried the linked pull request branch and it appears to solve the problem
for me. Thanks!
--
This is an automated message from the Apache Git Service.
To respond to the messa
MaxAller opened a new issue, #3177:
URL: https://github.com/apache/logging-log4j2/issues/3177
## Description
On [this
page](https://logging.apache.org/log4j/2.x/manual/thread-context.html#init)
([in
source](https://github.com/apache/logging-log4j2/blob/2.x/src/site/antora/modules/RO
jaykataria commented on issue #2769:
URL:
https://github.com/apache/logging-log4j2/issues/2769#issuecomment-2458996673
Hi @ppkarwasz
Made some good progress but needed your input on something:
I am not sure if we should add type checking here:
```
if (methodName
ppkarwasz commented on issue #2769:
URL:
https://github.com/apache/logging-log4j2/issues/2769#issuecomment-2459096985
**Note**: I noticed that some of our builders have complex conventions for
the name of the setter: the setter for an `isUnicode` field should be called
`setUnicode` and **n
ppkarwasz commented on issue #2169:
URL:
https://github.com/apache/logging-log4j2/issues/2169#issuecomment-2459451988
@Baixiu-code,
- Are you using Log4j Core `2.24.1`?
- Did you try using `com.lmax:disruptor` version `4.0.0`?
- What is the status of the **polling** thread? The
ppkarwasz opened a new pull request, #1:
URL: https://github.com/apache/logging-slf4j/pull/1
This adds a new `slf4j-to-log4j-api` bridge based on `log4j-slf4j2-impl`
from the `2.x` branch of Log4j.
--
This is an automated message from the Apache Git Service.
To respond to the message, ple
ppkarwasz opened a new pull request, #1:
URL: https://github.com/apache/logging-jdk/pull/1
This add a new `jpl-to-log4j-api` bridge based on `log4j-jpl` from the `2.x`
branch of Log4j.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to
ppkarwasz opened a new pull request, #2:
URL: https://github.com/apache/logging-slf4j/pull/2
This adds a new `log4j-api-to-slf4j` bridge based on `log4j-to-slf4j` from
the `2.x` branch of Log4j.
--
This is an automated message from the Apache Git Service.
To respond to the message, please
ppkarwasz opened a new pull request, #3:
URL: https://github.com/apache/logging-jdk/pull/3
This add a new `log4j-api-to-jul` bridge based on `log4j-to-jul` from the
`2.x` branch of Log4j.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on
github-advanced-security[bot] commented on PR #1:
URL: https://github.com/apache/logging-jdk/pull/1#issuecomment-2459612607
This pull request sets up GitHub code scanning for this repository. Once the
scans have completed and the checks have passed, the analysis results for this
pull reques
ppkarwasz opened a new pull request, #2:
URL: https://github.com/apache/logging-jdk/pull/2
This add a new `jul-to-log4j-api` bridge based on `jul-to-log4j` from the
`main` branch of Log4j.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log o
ppkarwasz commented on issue #2769:
URL:
https://github.com/apache/logging-log4j2/issues/2769#issuecomment-2459091744
@jaykataria,
> But the issue that I face is with such kind of setters, we are throwing an
error in such cases due to type checking:
> ```java
> private org.
github-advanced-security[bot] commented on PR #1:
URL: https://github.com/apache/logging-slf4j/pull/1#issuecomment-2459861207
This pull request sets up GitHub code scanning for this repository. Once the
scans have completed and the checks have passed, the analysis results for this
pull requ
Baixiu-code commented on issue #2169:
URL:
https://github.com/apache/logging-log4j2/issues/2169#issuecomment-2459214534
same issues. and cpu 100%. and t version is 3.4.2 .
--
This is an autom
jaykataria commented on issue #2769:
URL:
https://github.com/apache/logging-log4j2/issues/2769#issuecomment-2461336252
> Note: I noticed that some of our builders have complex conventions for the
name of the setter: the setter for an isUnicode field should be called
setUnicode and not
ppkarwasz commented on issue #2769:
URL:
https://github.com/apache/logging-log4j2/issues/2769#issuecomment-2461500874
@jaykataria,
Great job! :100:
> > Note: I noticed that some of our builders have complex conventions for
the name of the setter: the setter for an isUnicod
swebb2066 closed issue #425: Creating a static NDC causes a segfault on exit in
1.3.0
URL: https://github.com/apache/logging-log4cxx/issues/425
--
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 sp
swebb2066 merged PR #426:
URL: https://github.com/apache/logging-log4cxx/pull/426
--
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 closed issue #3177: Confusing example in Thread Context documentation
URL: https://github.com/apache/logging-log4j2/issues/3177
--
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
ppkarwasz closed pull request #3038: Remove `log4j-core` dependency from SLF4J
bridges
URL: https://github.com/apache/logging-log4j2/pull/3038
--
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 spe
ppkarwasz commented on PR #3038:
URL: https://github.com/apache/logging-log4j2/pull/3038#issuecomment-2460862741
Closing this, since we discussed an [alternative solution on
`dev@logging`](https://lists.apache.org/thread/tk8k8bnmy11b08xftr4p37yzgghpf61j).
--
This is an automated message f
ppkarwasz commented on PR #2924:
URL: https://github.com/apache/logging-log4j2/pull/2924#issuecomment-2460865426
As [discussed on
`dev@logging`](https://lists.apache.org/thread/tk8k8bnmy11b08xftr4p37yzgghpf61j)
all the bridges will be removed from Log4j Core 3.x, since they don't belong
he
ppkarwasz merged PR #2924:
URL: https://github.com/apache/logging-log4j2/pull/2924
--
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
23 matches
Mail list logo
