Warning: This build has drifted.
The coverage report for this pull request build may be inaccurate because its base commit is no longer the HEAD of its target branch.
This means it includes changes from outside the original pull request, including, potentially, unrelated coverage changes.

    • Learn more: For more information on this, see Tracking coverage changes for pull request builds.
    • Fix now: For a quick fix, rebase this PR at GitHub. Your next report should be accurate.
    • Prevent going forward: To avoid this issue with future PRs, see these Recommended CI Configurations.

fix: guard against nil callback on unknown reply id in Dispatch

Dispatch ignored the loaded bool from callbacks.LoadAndDelete and
dereferenced cb.noReply directly. A reply whose id has no pending
callback (duplicate or unknown reply) would deref a nil
*protocolCallback and panic the dispatch goroutine. Upstream throws
"Cannot find command to respond"; guard and ignore the stray reply.

This becomes more reachable with the re-entrant pump, which runs
Dispatch from inside a blocking call made in an event handler.