This is an automated email from the ASF dual-hosted git repository. FreeAndNil pushed a commit to branch Feature/316-content-loss in repository https://gitbox.apache.org/repos/asf/logging-log4net.git
commit 7de84b7d3dc04707cac3216ff79696363169e044 Author: Jan Friedrich <[email protected]> AuthorDate: Thu Sep 3 23:26:40 2026 +0200 cite the audit findings behind the Ext.Mail and syslog work #314 The Ext.Mail send rework answers f004 and the remote syslog queue and pump work answers f034, but neither pair named the finding. The other five 314 and 315 entries stay unattributed: they are our own, not audit findings. --- src/changelog/3.5.0/314-ext-mail-background-sender.xml | 2 +- src/changelog/3.5.0/314-ext-mail-send-timeout.xml | 2 +- src/changelog/3.5.0/314-remote-syslog-background-sender.xml | 2 +- src/changelog/3.5.0/314-remote-syslog-socket-and-connect.xml | 2 +- 4 files changed, 4 insertions(+), 4 deletions(-) diff --git a/src/changelog/3.5.0/314-ext-mail-background-sender.xml b/src/changelog/3.5.0/314-ext-mail-background-sender.xml index f16ce22f..acbe9d09 100644 --- a/src/changelog/3.5.0/314-ext-mail-background-sender.xml +++ b/src/changelog/3.5.0/314-ext-mail-background-sender.xml @@ -10,6 +10,6 @@ for the SMTP server. The queue holds `sendQueueSize` mails (500) and a logging call waits at most `enqueueTimeoutMillis` (5000) for room in it. Failures are still reported to the error handler, but after the logging call has returned, and `Flush` now honours its timeout - (implemented by @FreeAndNil) + (audit da18b6fd-f004, implemented by @FreeAndNil) </description> </entry> diff --git a/src/changelog/3.5.0/314-ext-mail-send-timeout.xml b/src/changelog/3.5.0/314-ext-mail-send-timeout.xml index 2a8a0469..8ec6b8f6 100644 --- a/src/changelog/3.5.0/314-ext-mail-send-timeout.xml +++ b/src/changelog/3.5.0/314-ext-mail-send-timeout.xml @@ -9,6 +9,6 @@ per operation by default, and the mail goes out while the appender lock is held, so an unresponsive server suspended every thread logging through the appender. `SendTimeoutMillis` is a deadline for the send as a whole, because a per operation timeout still allows a multiple of - itself overall (implemented by @FreeAndNil) + itself overall (audit da18b6fd-f004, implemented by @FreeAndNil) </description> </entry> diff --git a/src/changelog/3.5.0/314-remote-syslog-background-sender.xml b/src/changelog/3.5.0/314-remote-syslog-background-sender.xml index 9ea954df..1894ef20 100644 --- a/src/changelog/3.5.0/314-remote-syslog-background-sender.xml +++ b/src/changelog/3.5.0/314-remote-syslog-background-sender.xml @@ -9,6 +9,6 @@ stopped accepting datagrams grew it until the process ran out of memory, and shutdown waited five seconds and then abandoned a drain that had no limit of its own. It now holds `sendQueueSize` datagrams (500), a logging call waits at most `enqueueTimeoutMillis` (5000) for room, losses are - counted and reported, and `Flush` honours its timeout (implemented by @FreeAndNil) + counted and reported, and `Flush` honours its timeout (audit da18b6fd-f034, implemented by @FreeAndNil) </description> </entry> diff --git a/src/changelog/3.5.0/314-remote-syslog-socket-and-connect.xml b/src/changelog/3.5.0/314-remote-syslog-socket-and-connect.xml index fb2185c7..2785a792 100644 --- a/src/changelog/3.5.0/314-remote-syslog-socket-and-connect.xml +++ b/src/changelog/3.5.0/314-remote-syslog-socket-and-connect.xml @@ -9,6 +9,6 @@ connection its background pump owns, but also inherited one from `UdpAppender` that nothing ever used, which bound `localPort` twice. A pump that cannot connect now reports it as well, instead of ending unobserved and leaving every later event queued behind a sender that is gone - (implemented by @FreeAndNil) + (audit da18b6fd-f034, implemented by @FreeAndNil) </description> </entry>
