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
As a contract developer I would like to be able to write robust end-to-end tests that include verification of the signer account balance to confirm the attached storage deposits are correctly handled (kept or refunded). To be able to correctly reconcile the resulting account balance I first need to be able to determine how much tokens were burnt to cover gas costs. Then the remaining balance difference is deposit-related and can be used to check the correctness of deposit handling. Unfortunately, it seems that the Rust version of the Workspaces does not report tokens_burnt. The Workspaces Rust version of the ExecutionOutcome struct is out of sync with core version (as declared in https://github.com/near/nearcore/blob/master/core/primitives/src/transaction.rs) where the latter includes some extra fields (tokens_burnt being one of them).
The text was updated successfully, but these errors were encountered:
As a contract developer I would like to be able to write robust end-to-end tests that include verification of the signer account balance to confirm the attached storage deposits are correctly handled (kept or refunded). To be able to correctly reconcile the resulting account balance I first need to be able to determine how much tokens were burnt to cover gas costs. Then the remaining balance difference is deposit-related and can be used to check the correctness of deposit handling. Unfortunately, it seems that the Rust version of the Workspaces does not report tokens_burnt. The Workspaces Rust version of the ExecutionOutcome struct is out of sync with core version (as declared in https://github.com/near/nearcore/blob/master/core/primitives/src/transaction.rs) where the latter includes some extra fields (tokens_burnt being one of them).
The text was updated successfully, but these errors were encountered: