[CLI] Add debug prints for execution time of a tx / dry run #19374
Conversation
|
The latest updates on your projects. Learn more about Vercel for Git ↗︎
3 Skipped Deployments
|
|
Does devs typically turn on debug logging? I was more of thinking about explicitly print out the elapsed time |
Usually not, but also not sure why a dev would be interested in knowing the time it took to prepare the transaction or execution time from the CLI(they could just use So far, we kept info-like output only via tracing and focused on showing relevant information. Would love to hear your thoughts if you think more "meta" output should be shown. Finally, from the slack discussion I thought this was for cases where maybe an execution is slow, so one could run the CLI command with debug to see what's going on. We could document it. |
## Description Adds debug prints for preparing a tx and executing it. Similarly, adds debug prints for executing a dry run. ## Test plan How did you test the new or updated feature? --- ## Release notes Check each box that your changes affect. If none of the boxes relate to your changes, release notes aren't required. For each box you select, include information after the relevant heading that describes the impact of your changes that a user might notice and any actions they must take to implement updates. - [ ] Protocol: - [ ] Nodes (Validators and Full nodes): - [ ] Indexer: - [ ] JSON-RPC: - [ ] GraphQL: - [x] CLI: Added debug prints for preparing a tx and executing it. Similarly, adds debug prints for executing a dry run. Use `RUST_LOG=debug sui` to see the extra information printed on the terminal. - [ ] Rust SDK: - [ ] REST API:
Description
Adds debug prints for preparing a tx and executing it. Similarly, adds debug prints for executing a dry run.
Test plan
How did you test the new or updated feature?
Release notes
Check each box that your changes affect. If none of the boxes relate to your changes, release notes aren't required.
For each box you select, include information after the relevant heading that describes the impact of your changes that a user might notice and any actions they must take to implement updates.
RUST_LOG=debug suito runsuiCLI with the debug logging enabled.