Open jacobleygonie opened 2 years ago
I get the same error but it is not specific to dumpState, sometimes checkState does it too. It's really annoying.
@jacobleygonie, @Alex1304, thank you for reporting the issue :pray:
Mandos is writing non-printable characters in the stdout, in this case. E.g.
Scenario: adder.scen.json ... world state dump:
{
"address:user": {
"nonce": "1",
"balance": "1000",
"esdt": {
"str:TOKENA-abcdef": {
"instances": [
{
"nonce": "0",
"balance": "100"
}
],
"lastNonce": "0"
}
}
},
"sc:contract": {
"nonce": "0",
"balance": "0",
"owner": "address:user"
},
"address:\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff#ff": {
"nonce": "0",
"balance": "0"
}
}
We are working on a fix.
Any updates on this? It's pretty grizzly writing these tests without this functionality.
I am having decoding errors in mandos tests when dumping the state after sending an ESDT token to a contract. Currently using elrond-wasm v0.27.2. The error is not triggered when sending EGLD to the contract.
Below is an example of contract+test triggering the error:
The Smart Contract
The Test (dumpState at the end)
The Error