Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
[BUGFIX][CLI] verify-bytecode-meter returns module ticks (#16900)
## Description We were returning the ticks used for the last function as the verifier ticks, which is not correct. Returning the ticks used for the last function is also not particularly useful, but I will fix that in a follow-up PR. ## Test Plan ``` sui-framework/deepbook$ cargo run --bin sui -- \ client verify-bytecode-meter Total number of linter warnings suppressed: 3 (filtered categories: 2) Running bytecode verifier for 7 modules ╭──────────────────────────────────╮ │ Module will pass metering check! │ ├────────┬────────────┬────────────┤ │ │ Module │ Function │ │ Max │ 16000000 │ 16000000 │ │ Used │ 5869980 │ 7040 │ ╰────────┴────────────┴────────────╯ ``` ## Stack - #16899 --- If your changes are not user-facing and do not break anything, you can skip the following section. Otherwise, please briefly describe what has changed under the Release Notes section. ### Type of Change (Check all that apply) - [ ] protocol change - [x] user-visible impact - [ ] breaking change for a client SDKs - [ ] breaking change for FNs (FN binary must upgrade) - [ ] breaking change for validators or node operators (must upgrade binaries) - [ ] breaking change for on-chain data layout - [ ] necessitate either a data wipe or data migration ### Release notes Fixes a bug where `sui client verify-bytecode-meter` incorrectly returned the ticks used by the last function to be verified as the ticks used by the last module verified.
- Loading branch information