Peer listings now warn when the session walk didn't finish, so partial lists aren't mistaken for complete.
What's wrong with this entry?
listAllPeers now tells the model when bridge rows are present but the session walk did not finish, so partial results are not mistaken for the full set.
- The previous bridge-population field was replaced with a
bridgeWalkFailedflag, set when the walk failed or the handle produced no usable result. - With bridge rows present and the walk failed, the listing appends: "list incomplete just now — those rows carry no [ref] and are not messageable by name until a later listing completes".
- A helper that reported bridge population separately was removed.
bridgeWalkFailed
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.234
Messages injected by a host are classified separately from peer messages
Both mention cross
-
v2.1.234
Cross-session control requests check ids more carefully
Both mention cross
-
v2.1.234
Notice acks now wait for the record to persist
Both mention cross