From 23ec0a7b811a0e986fe2d2cb51fffe8f10f7a57d Mon Sep 17 00:00:00 2001 From: Johnathan Corgan Date: Mon, 17 Aug 2026 06:18:49 +0000 Subject: [PATCH] Record the path-MTU refusal correlator in the changelog Of the seven commits on this branch that the maintenance line does not carry, one changes something an operator can observe: the sub-floor path MTU warning now names the request it refused, so the line can be tied to an exchange. The other six are test pinning, constant re-sourcing and comment corrections with no observable effect, and are deliberately left out rather than written up to make the branch look served. --- CHANGELOG.md | 11 +++++++++++ 1 file changed, 11 insertions(+) diff --git a/CHANGELOG.md b/CHANGELOG.md index 0488b4b1..8df76745 100644 --- a/CHANGELOG.md +++ b/CHANGELOG.md @@ -308,6 +308,17 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0 behaviour of the shipped binaries changes; this affects only callers using `fips` as a library. +- The warning raised when a lookup response carries a path MTU below the + actionable floor now names the request it refused, as a `request_id` field on + the log line. Every other warning that handler emits already carried the + correlator, and this one could not: it is raised while the cached-coordinates + effect is applied, after the response itself has gone out of scope. An + operator reading the refusal therefore had a counter and a peer name but no + way to tie the line to a particular exchange, or to the sibling lines logged + for it. **Only the log line changes** — the response is still accepted, the + coordinates are still cached, the sub-floor path MTU is still discarded, and + the same counter is still charged. + ### Deprecated - The `discovery` metric-family key (control-socket JSON). It is dual-emitted