ppkarwasz commented on code in PR #406:
URL: https://github.com/apache/logging-parent/pull/406#discussion_r2133472810
##
.github/workflows/verify-reproducibility-reusable.yaml:
##
@@ -61,7 +61,30 @@ jobs:
with:
distribution: zulu
java-version: ${{
Copilot commented on code in PR #406:
URL: https://github.com/apache/logging-parent/pull/406#discussion_r2133469530
##
.github/workflows/verify-reproducibility-reusable.yaml:
##
@@ -61,7 +61,30 @@ jobs:
with:
distribution: zulu
java-version: ${{ in
ppkarwasz commented on PR #389:
URL: https://github.com/apache/logging-parent/pull/389#issuecomment-2951942239
In the long run I would prefer to use a solution like Mimír to ensure that
we only have a single reliable cache **without** locally built artifacts that
can be reused in all workfl
ppkarwasz opened a new pull request, #406:
URL: https://github.com/apache/logging-parent/pull/406
This change introduces a separate cache specifically for the
`verify-reproducibility` workflow to ensure it does not reuse artifacts cached
by other workflows. By isolating its cache, we ensure
ppkarwasz commented on issue #3336:
URL:
https://github.com/apache/logging-log4j2/issues/3336#issuecomment-2951766099
Hi @jhl221123,
> I'd be grateful if you could take a look when you have a moment. Thanks!
Thanks so much for your PR—and apologies for the delay in reviewing it
github-actions[bot] merged PR #193:
URL: https://github.com/apache/logging-log4j-transform/pull/193
--
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: noti
kamilkrzywanski opened a new pull request, #3719:
URL: https://github.com/apache/logging-log4j2/pull/3719
We should improve the implementation of StatusLogger by extracting all
regular expressions used for property normalization and matching into clearly
named, precompiled Pattern constants
FreeAndNil closed issue #244: v3.1.0 - Exception with RollingFileAppender when
files are already present
URL: https://github.com/apache/logging-log4net/issues/244
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL ab
FreeAndNil commented on issue #252:
URL:
https://github.com/apache/logging-log4net/issues/252#issuecomment-2949997101
@lcrok thanks for reporting the issue.
"log.GetAppender(appenderName) == null" + "log.AddAppender(fileAppender)" is
not thread safe.
When multiple threads call your Ge
FreeAndNil merged PR #251:
URL: https://github.com/apache/logging-log4net/pull/251
--
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
jhl221123 commented on issue #3336:
URL:
https://github.com/apache/logging-log4j2/issues/3336#issuecomment-2949633820
Hi @ppkarwasz,
I came across #3176. Noticing the previous pull request had been closed,
I've now opened a new PR to address this.
I'd be grateful if you could
jhl221123 opened a new pull request, #3718:
URL: https://github.com/apache/logging-log4j2/pull/3718
This pull request resolves issue #3336 by fixing the script resolution
failure that occurred when a `` element was placed before the
`` block in a configuration file.
> [!IMPORTANT]
eimhof commented on issue #244:
URL:
https://github.com/apache/logging-log4net/issues/244#issuecomment-2949158746
Thx @gdziadkiewicz, I can confirm that this fixes my issue. Looking forward
to a new release.
--
This is an automated message from the Apache Git Service.
To respond to the m
13 matches
Mail list logo
