When another session supersedes yours, the bridge closes once and reports it instead of trying to re-register.
What's wrong with this entry?
The bridge no longer treats close code 4090 as "session registration went stale, re-registering". A supersession close is now latched once, logged, and reported as transport_closed_4090, with archiving suppressed.
latched a stashed supersession close
Strings lifted out of the shipped bundle, so the claim above can be checked against them.
Related
Other releases about the same thing. Found by shared names or similar wording; neither means one caused the other.
-
v2.1.236
Remote bridge waits for the disconnect notice, and an inbox fetch that is always off
Both mention bridge
-
v2.1.236
Bridge shuts down cleanly on SIGHUP
Both mention bridge
-
v2.1.238
Three new remote bridge flags for auth recovery and session end
Both mention bridge