Testnet4 - 1.23 #12
Closed
Testnet4 - 1.23 #12
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…16789) ## Description There is no reason to add them one-by-one in-place, from both consensus transaction and owned object transaction path. In fact, in the end we will have all transactions to be scheduled. We can add them all in one function in the end. This makes this piece of code slightly simpler. ## Test Plan CI --- 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 - [ ] 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
…enLabs#16797) ## Description I found that it would cause quick OOM when indexer has many objects to resolve, although many object types are the same, so this PR improves that by only resolving unique struct tags. ## Test Plan on rpc-benchmark, run with this PR and the OOM gets much better although on some huge checkpoints of size 50MB+, oom still happens a couple of times (with a solution in a coming PR). --- 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 - [ ] 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
## Description
Today, every query in a graphql request separately makes a query for the
available range. This means that every query is self-consistent (so if
it is paginated, you will continue paginating the state at the same
checkpoint as you started), but if you issue multiple queries at the
same time, each query in the graphql request may see different available
range values.
This can result in inconsistencies in the results of disjoint queries in
the same request:
```
query {
alice: address(address: 0xA11CE) {
objects { nodes { digest } }
}
bob: address(address: 0xB0B) {
objects { nodes { digest } }
}
}
```
The above query might witness the same object twice, or no times, based
on timing, if issued around the time that Alice transfers that object to
Bob.
This PR adds cross-query consistency by launching a background task that
periodically updates the available range, which gets passed to the
graphql service. Every top-level query in the request will inherit this
available range. Additionally, instead of making a separate fetch when
`Query.availableRange` is selected for, the resolver will simply return
the available range from the background task.
Subsequent PRs will change `checkpoint_viewed_at` from `Option<u64>` to
`u64` and simplify the logic around handling consistency for nested
fields.
## Test Plan
Existing tests should pass. Because of the background task, we also need
to wait for the graphql service to "catch up" to the latest checkpoint
---
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
- [ ] 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
## Description Add interfaces for fetching randomness: `RandomGenerator` is a PRG with a seed that is derived from the global randomness (which is the same between randomness rounds) and a fresh UID (which is guaranteed to be unique by the framework). In other words, the seed is unpredictable without knowing the global randomness, and different for each created generator (thus not predictable even by different functions invoked for the same tx). `RandomGenerator` manages an internal state with a buffer of random bytes derived using the PRG, and provides high level functions for deriving integers from those random bytes. ## Test Plan Unit tests --- If your changes are not user-facing and not a breaking change, you can skip the following section. Otherwise, please indicate what changed, and then add to the Release Notes section as highlighted during the release process. ### Type of Change (Check all that apply) - [x] protocol change - [ ] user-visible impact - [ ] breaking change for a client SDKs - [x] breaking change for FNs (FN binary must upgrade) - [x] 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 Add Move interfaces for generating secure random values.
## Description Describe the changes or additions included in this PR. ## Test Plan How did you test the new or updated feature? --- 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 - [ ] 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
## Description Update fastcrypto pointer ## Test Plan CI --- 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 - [ ] 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
## Description This PR makes it so that `write_to_lock` in dependency graph code only populates the `Move.lock` with the relevant state it ought to, leaving everything else in the lock file alone. This is in contrast to the current "wipe everything, populate dependencies, and expect orthogonal information to be populated afterwards on every invocation". This applies to the following TOML values in `Move.lock`: - `manifest_digest` - `deps_digest` - `dependencies` (for root package) - `dev-dependencies` (for root package) - `[[move.packages]]` array of table ## Test Plan Updated tests. Lock file re-generation may remove empty lines in `Move.lock` and is a user-visible change, though not semantically meaningful. --- 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
## Description Example code swapped the ordering of `to_address` and the parameters as a result of MystenLabs#16566 ## Test Plan Visual inspection --- 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 - [ ] 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
## Description Does what it says on the tin (read: makes the code all shiny!) Public use funs: ``` ascii.move 10: public use fun std::string::from_ascii as String.to_string; vector.move 10: public use fun std::string::utf8 as vector.to_string; 14: public use fun std::string::try_utf8 as vector.try_to_string; 17: public use fun std::ascii::string as vector.to_ascii_string; 21: public use fun std::ascii::try_string as vector.try_to_ascii_string; ``` ## Test Plan All the tests still work as expected, plus hand-analysis of decompiled bytecode matches 1:1. --- 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 - [ ] 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
Signed-off-by: Carlos Baez <[email protected]>
## Description Fix check against `MAX_SUPPLY` to test the current supply, rather than the value of the next NFT to be issued. The doc comment for `burn` indicates that we should be able to mint new NFTs at higher values if earlier NFTs have been burned to free up supply. ## Test Plan CI Co-authored-by: stefan-mysten <[email protected]>
## Description This PR adds support for formatting functions definitions, including native ones, but excluding macros (to make these PRs more incremental - macros are a bit more subtle). It also fixes an omission from the support for formatting structs (phantom type parameters). ## Test Plan A new test has been added.
Signed-off-by: Carlos Baez <[email protected]>
## Description Describe the changes or additions included in this PR. ## Test Plan How did you test the new or updated feature? --- 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 - [ ] 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
) ## Description adds an graphql endpoint to verify a zklogin signature for the given bytes and zklogin signature. ## Test Plan to run e2e test ``` cargo test --features "pg_integration" --package sui-graphql-rpc --test e2e_tests -- tests::test_zklogin_sig_verify --exact --nocapture ``` to run locally and test ``` cargo run --bin sui-test-validator -- --with-indexer --pg-port 5432 --pg-db-name sui_indexer_v2 --graphql-host 127.0.0.1 --graphql-port 9125 ``` go to http://localhost:9125/ enter query: ``` query Zklogin($bytes: String!, $signature: String!, $intent_scope: Int!, $author: SuiAddress!) { verifyZkloginSignature( bytes: $bytes signature: $signature intentScope: $intent_scope author: $author ) { errors } } ``` enter variable ``` { "bytes": "AAABACACAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgEBAQABAAAcpgUkGBwS5nPO79YXkjMyvaRjGS57hqxzfyd2yGtejwGbB4FfBEl+LgXSLKw6oGFBCyCGjMYZFUxCocYb6ZAnFwEAAAAAAAAAIJZw7UpW1XHubORIOaY8d2+WyBNwoJ+FEAxlsa7h7JHrHKYFJBgcEuZzzu/WF5IzMr2kYxkue4asc38ndshrXo8BAAAAAAAAABAnAAAAAAAAAA==", "signature": "BQNNMTczMTgwODkxMjU5NTI0MjE3MzYzNDIyNjM3MTc5MzI3MTk0Mzc3MTc4NDQyODI0MTAxODc5NTc5ODQ3NTE5Mzk5NDI4OTgyNTEyNTBNMTEzNzM5NjY2NDU0NjkxMjI1ODIwNzQwODIyOTU5ODUzODgyNTg4NDA2ODE2MTgyNjg1OTM5NzY2OTczMjU4OTIyODA5MTU2ODEyMDcBMQMCTDU5Mzk4NzExNDczNDg4MzQ5OTczNjE3MjAxMjIyMzg5ODAxNzcxNTIzMDMyNzQzMTEwNDcyNDk5MDU5NDIzODQ5MTU3Njg2OTA4OTVMNDUzMzU2ODI3MTEzNDc4NTI3ODczMTIzNDU3MDM2MTQ4MjY1MTk5Njc0MDc5MTg4ODI4NTg2NDk2Njg4NDAzMjcxNzA0OTgxMTcwOAJNMTA1NjQzODcyODUwNzE1NTU0Njk3NTM5OTA2NjE0MTA4NDAxMTg2MzU5MjU0NjY1OTcwMzcwMTgwNTg3NzAwNDEzNDc1MTg0NjEzNjhNMTI1OTczMjM1NDcyNzc1NzkxNDQ2OTg0OTYzNzIyNDI2MTUzNjgwODU4MDEzMTMzNDMxNTU3MzU1MTEzMzAwMDM4ODQ3Njc5NTc4NTQCATEBMANNMTU3OTE1ODk0NzI1NTY4MjYyNjMyMzE2NDQ3Mjg4NzMzMzc2MjkwMTUyNjk5ODQ2OTk0MDQwNzM2MjM2MDMzNTI1Mzc2Nzg4MTMxNzFMNDU0Nzg2NjQ5OTI0ODg4MTQ0OTY3NjE2MTE1ODAyNDc0ODA2MDQ4NTM3MzI1MDAyOTQyMzkwNDExMzAxNzQyMjUzOTAzNzE2MjUyNwExMXdpYVhOeklqb2lhSFIwY0hNNkx5OXBaQzUwZDJsMFkyZ3VkSFl2YjJGMWRHZ3lJaXcCMmV5SmhiR2NpT2lKU1V6STFOaUlzSW5SNWNDSTZJa3BYVkNJc0ltdHBaQ0k2SWpFaWZRTTIwNzk0Nzg4NTU5NjIwNjY5NTk2MjA2NDU3MDIyOTY2MTc2OTg2Njg4NzI3ODc2MTI4MjIzNjI4MTEzOTE2MzgwOTI3NTAyNzM3OTExCgAAAAAAAABhAG6Bf8BLuaIEgvF8Lx2jVoRWKKRIlaLlEJxgvqwq5nDX+rvzJxYAUFd7KeQBd9upNx+CHpmINkfgj26jcHbbqAy5xu4WMO8+cRFEpkjbBruyKE9ydM++5T/87lA8waSSAA==", "intent_scope": 0, "author": "0x1ca60524181c12e673ceefd617923332bda463192e7b86ac737f2776c86b5e8f" } ``` run and got response: ``` { "data": { "verifyZkloginSignature": { "errors": null } } } ``` --- 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 - [ ] 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 --------- Co-authored-by: Will Yang <[email protected]>
## Description Enable [EC ops](https://github.com/MystenLabs/sui/blob/3cdb1f38616b5d456e468c72892bd53e39dc42fe/crates/sui-framework/packages/sui-framework/sources/crypto/bls12381.move#L27-L28) on all networks (currently enabled only on devnet). The plan is to cherrypick this to release 1.21, but only changing its protocol config to version 41. Increasing here the version of main to be larger than the new one in the release. ## Test Plan How did you test the new or updated feature? --- 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 - [ ] 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
Redesigns RandomnessManager to avoid `Inner` pattern since that interacts poorly with async/await.
## Description title, explorer has been subsetted and we can now clean up some dead codes ## Test Plan CI and local run to make sure that OLTP indexer still works. --- 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 - [ ] 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
## Description - One pager migration guide ## Test Plan - 👀 --- 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 - [ ] 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 --------- Co-authored-by: Ronny Roland <[email protected]>
## Description - Changed layout of primitive types - Added sui references for storage ## Test Plan - 👀 --- 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 - [ ] 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 --------- Co-authored-by: Cam Swords <[email protected]>
## Description adding links to go and python sdks ## Test Plan visual inspection + manual test --- 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 - [ ] 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
## Description This is the 1st step of supporting tonic in Mysticeti: - Build tonic client and service stubs. - Implement tonic client and service for consensus messages. - Allow switching between anemo and tonic in MysticetiManager via env var. If the results are promising, we can start looking into: - Tuning tonic parameters. - Implementing streaming. - Implementing peer authentications if we decide to roll this out to testnet. ## Test Plan CI Private testnet deployment --- 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 - [ ] 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
## Description as title ## Test Plan CI --- 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 - [ ] 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
## Description Describe the changes or additions included in this PR. ## Test Plan How did you test the new or updated feature? --- 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 - [ ] 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
…ystenLabs#16814) ## Description In the data ingestion workers, when send channels return `Err` it is a sign the processing pipeline is being closed, but right now this can lead to panics due to the use of `expects`. This PR replaces these with break or return statements, and ensures that all workers are finished before returning. ## Test Plan Unit tests are run.
Signed-off-by: Carlos Baez <[email protected]>
## Description Describe the changes or additions included in this PR. ## 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: - [ ] CLI: - [ ] Rust SDK:
## Description - Added placeholders for type inference `_` ## Test Plan - Added tests --- 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 Move 2024.alpha now supports placeholders for type inference `_` --------- Co-authored-by: Todd Nowacki <[email protected]> Co-authored-by: Cam Swords <[email protected]>
Signed-off-by: Carlos Baez <[email protected]>
## Description Remove signal as it is breaking windows build, we don't really need it
## Description - Most usages of it have already been removed, just finally removing it from the file format ## Test plan - CI --- ## 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: - [ ] CLI: - [ ] Rust SDK:
## Description * Fix tar ball structure * Simplify the code ## Test plan https://github.com/MystenLabs/sui/actions/runs/8637810185
Signed-off-by: Carlos Baez <[email protected]>
Signed-off-by: Carlos Baez <[email protected]>
Signed-off-by: Carlos Baez <[email protected]>
Fix function name typo ## Description Fix spelling transposition `create_sword` actually referred to `sword_create` function ## Test plan N/A
## Description Reverting change to L2 accessor in Deepbook causing error for market makers. ## Test plan How did you test the new or updated feature? Reverting changes, no testing needed. ## 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. - [x] Protocol: Deepbook changes will be reverted - [ ] Nodes (Validators and Full nodes): - [ ] Indexer: - [ ] JSON-RPC: - [ ] GraphQL: - [ ] CLI: - [ ] Rust SDK:
…6806) ## Description Extend the existing checkpoint watermark task to also report the current epoch. Additionally set up a watch channel to notify listeners on epoch change. ## Test Plan How did you test the new or updated feature? --- 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 - [ ] 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
## Description - Removing unnecessary enum following `CompiledScript` removal MystenLabs#17113 ## Test plan - CI --- ## 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: - [ ] CLI: - [ ] Rust SDK:
…7105) ## Description Add ability to parse i128 type arrays from snowflake returned as arrow arrays. Also fix a small issue with metric handling ## Test plan How did you test the new or updated feature? Running locally works
## Description during the backfill, all tables except objects snspshot are committed all together and day can finish from genesis to latest in 4-5 days after recent optimization, however the objects_snapshot table took longer. This PR is to backfill objects snapshot in 2 modes - during backfill, just populate it with new object changes and stay updated - when close to backfill finish, we switch to the original intentionally lagging update mode ## Test plan local run and benchmark to monitor the new perf and correctness --- ## 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: - [ ] CLI: - [ ] Rust SDK:
…handler (MystenLabs#17108) ## Description The metric is added to AuthorityMetrics instead of EpochMetrics. So this PR also does some pluming to make `process_consensus_transactions` to take AuthorityMetrics. ## 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: - [ ] CLI: - [ ] Rust SDK:
## Description Sui v1.23.0 Branch cut framework bytecode snapshot ## Test plan `cargo run --bin sui-framework-snapshot`
Signed-off-by: Carlos Baez <[email protected]>
Sui testnet v1.23.0 release
Signed-off-by: Carlos Baez <[email protected]>
Signed-off-by: Carlos Baez <[email protected]>
Signed-off-by: Carlos Baez <[email protected]>
Signed-off-by: Carlos Baez <[email protected]>
Signed-off-by: Carlos Baez <[email protected]>
Signed-off-by: Carlos Baez <[email protected]>
Signed-off-by: Carlos Baez <[email protected]>
Signed-off-by: Carlos Baez <[email protected]>
Signed-off-by: Carlos Baez <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
No description provided.