Inbound peer messages are no longer mistaken for your own when running inside a container.
What's wrong with this entry?
Inbound peer messages are no longer misattributed to this process when the session runs as PID 1, which is common inside containers.
- the self-sent check now takes the pid as a parameter rather than reading it implicitly
- returns false outright when that pid is 1, so no false
selfSentmatch - pairs with the ancestor-walk change above
selfSent
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