Skip to content
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 2 additions & 2 deletions docs/develop/contracts/debug-locally.md
Original file line number Diff line number Diff line change
Expand Up @@ -105,7 +105,7 @@ near call simple-state.$REPRO_ACCOUNT get_status "{\"account_id\":\"$REPRO_ACCOU

Now let's reproduce this cross-contract call locally.

1. Spin up a sandbox node by following [this guide](https://docs.near.org/docs/develop/contracts/sandbox). **Don't start the sandbox node yet.**
1. Spin up a sandbox node.
2. Run the `get-sandbox-repro-genesis` tool to fetch information. This assumes you have the sandbox node's home dir in /tmp/near-sandbox.

```bash
Expand Down Expand Up @@ -133,7 +133,7 @@ near call cross-contract.$REPRO_ACCOUNT set_in_other_contract --accountId $REPRO
near call simple-state.$REPRO_ACCOUNT get_status "{\"account_id\":\"$REPRO_ACCOUNT\"}" --accountId $REPRO_ACCOUNT
```

You should see that the status has been successfully set to "world". If you're debugging a contract bug and want to avoid regression in the future, it's recommended to keep the genesis generated by `get-sandbox0repro-genesis.js` as a fixture and write a test script to run the transaction on a sandbox node. You can refer to [this doc](https://docs.near.org/docs/develop/contracts/sandbox) about writing sandbox test script.
You should see that the status has been successfully set to "world". If you're debugging a contract bug and want to avoid regression in the future, it's recommended to keep the genesis generated by `get-sandbox0repro-genesis.js` as a fixture and write a test script to run the transaction on a sandbox node.

## Obtain Information from Testnet/Mainnet Manually

Expand Down