You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Misleading title, the command reliably works for the only thing we ever use it for, checking the number of messages in the mempool. But the hashes that it spits out are not actually the hashes of messages in the mempool (actually, they should be all the same hash).
The problem is that 'View' returns []SignedMessages, and the commands 'type' is an array of Message (not signed). This causes unmarshaling to not work right. We get the right number of items, but each of the items is empty because the data coming over the wire has no fields in common with the expected type.
This could probably be prevented by a check in the commands lib, cc @Stebalien
The text was updated successfully, but these errors were encountered:
Misleading title, the command reliably works for the only thing we ever use it for, checking the number of messages in the mempool. But the hashes that it spits out are not actually the hashes of messages in the mempool (actually, they should be all the same hash).
The problem is that 'View' returns
[]SignedMessage
s, and the commands 'type' is an array ofMessage
(not signed). This causes unmarshaling to not work right. We get the right number of items, but each of the items is empty because the data coming over the wire has no fields in common with the expected type.This could probably be prevented by a check in the commands lib, cc @Stebalien
The text was updated successfully, but these errors were encountered: