ppkarwasz commented on PR #350:
URL:
https://github.com/apache/logging-log4j-samples/pull/350#issuecomment-3069913098
Hi @MartyIX,
Thanks again for digging into this — even negative results are valuable, as
they help us identify what might be missing in the test project.
Based
github-actions[bot] merged PR #81:
URL: https://github.com/apache/logging-log4j-audit-sample/pull/81
--
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: not
dependabot[bot] opened a new pull request, #81:
URL: https://github.com/apache/logging-log4j-audit-sample/pull/81
[ caused by the use of a thread-local `LogBuilder`
pool.
The leak occurred because th
mordio commented on issue #260:
URL:
https://github.com/apache/logging-log4net/issues/260#issuecomment-3069116897
FYI: I am using `.NET Framework v4.8` for the project using log4net. So I
can confirm it works for that version.
--
This is an automated message from the Apache Git Service.
gmiscione commented on issue #3819:
URL:
https://github.com/apache/logging-log4j2/issues/3819#issuecomment-3068154118
I am no expert in low latency programming, but the use case you are
describing makes perfect sense. I don't know if Logback has support for
something similar to this poolin
10 matches
Mail list logo