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
When I use the testInvoke endpoint from Neo Express, I receive a "RVCount doesn't match with EvaluationStack" error.
The result appears to be fine when I use neoxp contract run contract method -r. However, changing the last parameter to -a account instead of -r returns a transaction hash that doesn't exist.
Looking at Neo Express logs, I found 20:04:15.91 akka://NeoSystem/user/$e Error Corruption: WriteBatch has wrong count'
I don't know if the problems are related.
To Reproduce
Useneoxp contract run <contract> <method> <params> -a genesis. Copy the transaction hash
Use neoxp show transaction <hash>
See error: "Neo.Network.RPC.RpcException: Unknown transaction/blockhash"
Or
Call 'invokeFunction' on the Neo Express RPC node.
Check the result: "Exception: RVCount doesn't match with EvaluationStack"
Expected behavior
The transaction must persist and be findable using the hash, and the invokeFunction RPC should return the correct value.
please complete the following information
OS: macOS
Version 3.7.3
Additional context
The problem does not affect nodes on the Testnet. It returns the correct value without exceptions.
The text was updated successfully, but these errors were encountered:
Describe the bug
neoxp contract run contract method -r
. However, changing the last parameter to-a account
instead of -r returns a transaction hash that doesn't exist.20:04:15.91 akka://NeoSystem/user/$e Error Corruption: WriteBatch has wrong count
'I don't know if the problems are related.
To Reproduce
neoxp contract run <contract> <method> <params> -a genesis
. Copy the transaction hashneoxp show transaction <hash>
Or
Expected behavior
The transaction must persist and be findable using the hash, and the invokeFunction RPC should return the correct value.
please complete the following information
Additional context
The problem does not affect nodes on the Testnet. It returns the correct value without exceptions.
The text was updated successfully, but these errors were encountered: