Peer-origin conflicts are labelled under the same cause as hook collisions.
What's wrong with this entry?
Conflicts originating from a peer are labelled with the same reason as hook collisions, so both show up under one cause instead of an unlabelled one.
return e === "collision" || e === "peer" ? "hook" : e;
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