Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
[CLI] Add ability to run verifier on an individual module (#16899)
## Description Adding a couple of features to the `verify-bytecode-meter` command: - Specify a `--module` (as bytecode) to verify. - Specify a protocol version to verify at. Also switches the `--package` path from a positional parameter to a flag, for symmetry with the new `--module` flag. ## Test Plan ``` sui-framework/deepbook$ cargo run --bin sui -- \ client verify-bytecode-meter sui-framework/deepbook$ cargo run --bin sui -- \ client verify-bytecode-meter --package . sui-framework/deepbook$ cargo run --bin sui -- \ move build sui-framework/deepbook$ cargo run --bin sui -- \ client verify-bytecode-meter --module build/DeepBook/bytecode_modules/clob.mv sui-framework/deepbook$ cargo run --bin sui -- \ # Errors client verify-bytecode-meter --package '.' \ --module build/DeepBook/bytecode_modules/clob.mv ``` --- 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 - Adds a `--module`/`-m` flag to `sui client bytecode-verify-meter` to verify some module bytecode. - Replaces the positional, optional package path parameter for this command with `--package`/`-p`.
- Loading branch information