Re: [PR] Scoped context (logging-log4j2)

2024-04-16 Thread via GitHub
jvz commented on PR #2438: URL: https://github.com/apache/logging-log4j2/pull/2438#issuecomment-2059683740 Yes, I meant `ThreadLocal`, oops. What I'm hoping for is an API in Log4j that can be easily implemented to support other runtimes without Log4j needing to be aware of them or depend on

Re: [PR] Disable JMX bean creation by default (logging-log4j2)

2024-04-16 Thread via GitHub
ppkarwasz commented on PR #2468: URL: https://github.com/apache/logging-log4j2/pull/2468#issuecomment-2059218518 @sdavids, Thank you for your contribution. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL

Re: [PR] Disable JMX bean creation by default (logging-log4j2)

2024-04-16 Thread via GitHub
ppkarwasz merged PR #2468: URL: https://github.com/apache/logging-log4j2/pull/2468 -- 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

Re: [PR] Bump io.netty:netty-bom from 4.1.108.Final to 4.1.109.Final (logging-log4j2)

2024-04-16 Thread via GitHub
ppkarwasz commented on PR #2471: URL: https://github.com/apache/logging-log4j2/pull/2471#issuecomment-2059194654 @dependabot recreate -- 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

Re: [PR] Bump com.h3xstream.findsecbugs:findsecbugs-plugin from 1.12.0 to 1.13.0 [logging-parent]

2024-04-16 Thread via GitHub
github-actions[bot] merged PR #159: URL: https://github.com/apache/logging-parent/pull/159 -- 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

[PR] Bump com.h3xstream.findsecbugs:findsecbugs-plugin from 1.12.0 to 1.13.0 [logging-parent]

2024-04-16 Thread via GitHub
dependabot[bot] opened a new pull request, #159: URL: https://github.com/apache/logging-parent/pull/159 Bumps [com.h3xstream.findsecbugs:findsecbugs-plugin](https://github.com/find-sec-bugs/find-sec-bugs) from 1.12.0 to 1.13.0. Release notes Sourced from https://github.com/find-se

Re: [PR] Add support for thread context map propagation (logging-log4j2)

2024-04-16 Thread via GitHub
ppkarwasz commented on PR #2442: URL: https://github.com/apache/logging-log4j2/pull/2442#issuecomment-2058762386 @remkop, > @ppkarwasz I don't think there is a garbage-free way to do Reactive streams. I would keep this simple and not worry about any garbage-free use cases. Tha

Re: [PR] Add support for thread context map propagation (logging-log4j2)

2024-04-16 Thread via GitHub
ppkarwasz closed pull request #2442: Add support for thread context map propagation URL: https://github.com/apache/logging-log4j2/pull/2442 -- 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 specif

Re: [PR] Add support for thread context map propagation (logging-log4j2)

2024-04-16 Thread via GitHub
remkop commented on PR #2442: URL: https://github.com/apache/logging-log4j2/pull/2442#issuecomment-2058746052 > Is there any usage for context propagation in the "garbage-free world"? My guess is that switching threads using Reactive streams or similar provides too much garbage for it to be

Re: [PR] Bump github/codeql-action from 3.24.10 to 3.25.0 [logging-parent]

2024-04-16 Thread via GitHub
github-actions[bot] merged PR #158: URL: https://github.com/apache/logging-parent/pull/158 -- 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

[PR] Bump github/codeql-action from 3.24.10 to 3.25.0 [logging-parent]

2024-04-16 Thread via GitHub
dependabot[bot] opened a new pull request, #158: URL: https://github.com/apache/logging-parent/pull/158 Bumps [github/codeql-action](https://github.com/github/codeql-action) from 3.24.10 to 3.25.0. Changelog Sourced from https://github.com/github/codeql-action/blob/main/CHANGELOG.m

Re: [PR] Add support for thread context map propagation (logging-log4j2)

2024-04-16 Thread via GitHub
ppkarwasz commented on PR #2442: URL: https://github.com/apache/logging-log4j2/pull/2442#issuecomment-2058655973 @remkop, Is there any usage for context propagation in the "garbage-free world"? My guess is that switching threads using Reactive streams or similar provides too much gar

Re: [PR] Add support for thread context map propagation (logging-log4j2)

2024-04-16 Thread via GitHub
ppkarwasz commented on code in PR #2442: URL: https://github.com/apache/logging-log4j2/pull/2442#discussion_r1566981486 ## log4j-api/src/main/java/org/apache/logging/log4j/spi/ExtendedThreadContext.java: ## @@ -0,0 +1,63 @@ +/* + * Licensed to the Apache Software Foundation (ASF

[I] Draft: [MS13] Automate website deployment (logging-log4j2)

2024-04-16 Thread via GitHub
vy opened a new issue, #2476: URL: https://github.com/apache/logging-log4j2/issues/2476 **Abstract:** This PR completes the STF milestone 13 by implementing the infrastructure to auto-deploy the Log4j website from project sources. Due to reasons detailed below, the website support is migrat