vy commented on PR #3655:
URL: https://github.com/apache/logging-log4j2/pull/3655#issuecomment-2892235695
@PAX523, thanks so much.
> What's the expected workflow now?
Maintainers finding time to check the commits are not tampered, kick CI, and
get it merged upon success.
--
vy merged PR #3655:
URL: https://github.com/apache/logging-log4j2/pull/3655
--
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...@lo
PAX523 commented on PR #3655:
URL: https://github.com/apache/logging-log4j2/pull/3655#issuecomment-2890118047
Good morning @vy. What's the expected workflow now? When will this PR be
merged?
--
This is an automated message from the Apache Git Service.
To respond to the message, please log
PAX523 commented on PR #3655:
URL: https://github.com/apache/logging-log4j2/pull/3655#issuecomment-2870851701
> @PAX523, thanks so much for the fix! It is a pleasure to collaborate with
an external contributor knowing how to write tests and adhere to existing
coding style. 🙇
>
> I've
vy commented on code in PR #3655:
URL: https://github.com/apache/logging-log4j2/pull/3655#discussion_r2081700663
##
log4j-core/src/main/java/org/apache/logging/log4j/core/message/ExtendedThreadInformation.java:
##
@@ -174,4 +174,14 @@ private void formatState(final StringBuilder
github-actions[bot] commented on PR #3655:
URL: https://github.com/apache/logging-log4j2/pull/3655#issuecomment-2863150146
Job
Requested goals
Build Tool Version
Build Outcome
Build Scan®
build-
PAX523 opened a new pull request, #3655:
URL: https://github.com/apache/logging-log4j2/pull/3655
Fix `ArrayIndexOutOfBoundsException` on invocation of
`Message.getFormattedMessage()` when any thread has no stack trace, which
occurs on some JVM implementations.
See issue: #3214
