mirror of
https://github.com/jmcorgan/fips.git
synced 2026-10-05 19:18:25 +00:00
Every sibling warning in the lookup response handler logs the request id, and this one could not: the coordinate-caching action did not carry it and the response is out of scope by the time the action is driven. An operator reading the refusal had a counter and no way to tie it to an exchange. Thread the id through the action, and assert it on the log line rather than on the action alone. Mutating either hop, the value the shell passes or the field on the warning, leaves the rest of the suite green, so the log line is the only place the pairing can be pinned. The tracing capture the config tests already had moves into the shared test helpers rather than being copied, and grows an async-scoped variant, since an async test cannot wrap its awaits in a closure.