A counter for queued peer messages exists but nothing reads it yet.
A queued peer-message count accessor is exported and re-bound, with no consumer in this build.
What's wrong with this entry?
The command queue module exposes a count of queued peer messages alongside its existing queue-length accessors.
getQueuedPeerMessageCountis exported and re-bound in the same place as the other queue accessors.- No consumer of the re-bound reference exists in this build, so it appears to be plumbing for a future caller.
getQueuedPeerMessageCount
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.248
Peer-session search and channel filters switched off
Both mention peer