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
There is a discrepancy in the shape of the block response for state proof responses.
Until recently there was also an error related to an integer key which caused two nil objects to be considered equal. After fixing that this error presented itself.
To reproduce, add the unit.stateproof.responses.msgp cucumber tag back to the unit test tags file.
Investigation required: what exactly is wrong with the state proof response?
The EXPECTED output includes block and cert as top level data. The ACTUAL output is just a block.
The blocks endpoint only includes block data in JSON responses, so this might be a mismatch in the type definition for JSON/MSGP formats.
More investigation needed to propose a solution.
winder
changed the title
Cucumber test unit.stateproof.responses.msgp does not work properly.
Cucumber BLOCK test unit.stateproof.responses.msgp does not work properly.
Jun 7, 2023
Additional block tests failing due to state proof messages (but for different reasons):
@unit.responses.statedelta
@unit.responses.txngroupdeltas
"spt": {
0: {
"n": 23963136
}
},
These have a number as key field which causes mismatches. These errors are likely related to the testing framework, where the previous block/cert issue is a design issue.
Subject of the issue
There is a discrepancy in the shape of the block response for state proof responses.
Until recently there was also an error related to an integer key which caused two nil objects to be considered equal. After fixing that this error presented itself.
To reproduce, add the
unit.stateproof.responses.msgp
cucumber tag back to the unit test tags file.Example error:
The text was updated successfully, but these errors were encountered: