Replies: 2 comments 3 replies
-
Definitely a reasonable request - the error message here is not very useful. Just to unpack this specific example: The error line comes from mina/src/lib/mina_base/account_update.ml Line 1932 in 6929a7e We probably got there via the The mina/src/lib/mina_base/zkapp_command.ml Lines 554 to 555 in 6929a7e It uses an early mina/src/lib/mina_base/zkapp_command.ml Line 564 in 6929a7e where it use mina/src/lib/mina_base/zkapp_command.ml Lines 574 to 579 in 6929a7e So you can see that at the point where the error occurs it doesn't know where update was that failed that check. I think if That check is applied over everything returned from
But, I'm not very familiar with the exact json serialization/deserialization here, so I could be wrong. Seems like the likely cause, though. This problem also manifests itself if you tried using mina/src/lib/mina_lib/mina_lib.ml Lines 989 to 999 in 6929a7e It only looks for the first ill-formed command, and concatenates all the errors it finds in that one command. Also some of those well-formedness errors might be a little unhelpful, particularly the |
Beta Was this translation helpful? Give feedback.
-
to add more context, I have a graphql query (proved and signed) from transaction that fails at devnet node level. we're trying to narrow down exact o1js code that we added that caused this error as we had multiple versions of this smart contract behaving well. Response
GraphQL request
|
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
Summary
As a developer, the way I create transactions and send them to Mina is via the Mina node's graphQL interface. Sometimes, I submit a transaction that is not valid and it will be rejected by the Mina node at the API level.
Note
There is a difference between a transaction being accepted by the node, and then failing and a transaction being rejected outright by the node
Expand the details section below for an example of a failing transaction
You can see that a developer can see what happened here, take educated next steps about what to do if the transaction was meant to succeed
One can't be sure exactly what the problem is from this context. But it's better than nothing.
When a transaction is rejected by the graphQL API, I get very little feedback about why.
What I would like to see:
Transaction details
Here is a sample transaction JSON that is rejected by devnet currently, and the graphQL response:
Response
Request
Beta Was this translation helpful? Give feedback.
All reactions