mirror of https://github.com/oxen-io/lokinet
Unbound callbacks also need arguments reversed
PR #1725 reversed argument orders but UnboundResolver was still using (from,to) ordering in its callbacks, which leaked through to make a wrong order in our reply function (which simply forwards arguments). This fixes that bug by making UnboundResolver callback argument order consistent (i.e. using to, from) with the PacketHandler argument order.pull/1728/head
parent
c0b8c87f81
commit
14c93e2b93
Loading…
Reference in New Issue