feat: allow to define storage to debug tenderly actions #54
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Sometimes, logs are insufficient (Tenderly hides them, and is hard to find in Sentry or they are missing)
It becomes super useful to be able to reproduce a failed execution in Tenderly Production, but locally.
This PR allows you to debug Locally failed executions
Workflow
We just get inside a failing execution to see the details:
There we can check the block number and the network.
Once we have this information, we get the Storage of Tenderly for that network.
Once we have the network, block and storage, we can reproduce the failure locally:
Additionally
This PR improves the logs in the
run_local.ts
script, so its easier to see where it fails.Now the script will return a non-zero error (
100
) if the execution of eitheraddContract
orcheckForAndPlaceOrder
or fails.