Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

start jwk consensus for google #12053

Merged
merged 2 commits into from
Feb 16, 2024
Merged

start jwk consensus for google #12053

merged 2 commits into from
Feb 16, 2024

Conversation

zjma
Copy link
Contributor

@zjma zjma commented Feb 15, 2024

Description

Test Plan

Copy link

trunk-io bot commented Feb 15, 2024

@zjma zjma marked this pull request as ready for review February 15, 2024 21:13
@zjma zjma enabled auto-merge (squash) February 15, 2024 21:13

This comment has been minimized.

This comment has been minimized.

@@ -116,6 +116,7 @@ proposals:
discussion_url: "https://github.com/aptos-foundation/AIPs/issues/331"
execution_mode: MultiStep
update_sequence:
- RawScript: data/proposals/aip_67_initialization.move
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think you need aptos-move/aptos-release-builder/data/proposals/aip_67_initialization.move full path cause release builder would be running on aptps-core directory.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

fixed

This comment has been minimized.

This comment has been minimized.

This comment has been minimized.

This comment has been minimized.

Copy link
Contributor

✅ Forge suite compat success on aptos-node-v1.8.3 ==> d5c49d60e4d5abfa911e90e08b2299277ee37fd1

Compatibility test results for aptos-node-v1.8.3 ==> d5c49d60e4d5abfa911e90e08b2299277ee37fd1 (PR)
1. Check liveness of validators at old version: aptos-node-v1.8.3
compatibility::simple-validator-upgrade::liveness-check : committed: 5480 txn/s, latency: 6128 ms, (p50: 6300 ms, p90: 9500 ms, p99: 10000 ms), latency samples: 191820
2. Upgrading first Validator to new version: d5c49d60e4d5abfa911e90e08b2299277ee37fd1
compatibility::simple-validator-upgrade::single-validator-upgrade : committed: 1780 txn/s, latency: 16244 ms, (p50: 18800 ms, p90: 22200 ms, p99: 22500 ms), latency samples: 92560
3. Upgrading rest of first batch to new version: d5c49d60e4d5abfa911e90e08b2299277ee37fd1
compatibility::simple-validator-upgrade::half-validator-upgrade : committed: 1772 txn/s, latency: 16222 ms, (p50: 19200 ms, p90: 22300 ms, p99: 22600 ms), latency samples: 92160
4. upgrading second batch to new version: d5c49d60e4d5abfa911e90e08b2299277ee37fd1
compatibility::simple-validator-upgrade::rest-validator-upgrade : committed: 3560 txn/s, latency: 9010 ms, (p50: 9500 ms, p90: 13500 ms, p99: 13800 ms), latency samples: 138840
5. check swarm health
Compatibility test for aptos-node-v1.8.3 ==> d5c49d60e4d5abfa911e90e08b2299277ee37fd1 passed
Test Ok

This comment has been minimized.

This comment has been minimized.

Copy link
Contributor

✅ Forge suite realistic_env_max_load success on d5c49d60e4d5abfa911e90e08b2299277ee37fd1

two traffics test: inner traffic : committed: 7371 txn/s, latency: 5175 ms, (p50: 4800 ms, p90: 6500 ms, p99: 12200 ms), latency samples: 3184400
two traffics test : committed: 100 txn/s, latency: 2169 ms, (p50: 2100 ms, p90: 2500 ms, p99: 3400 ms), latency samples: 1860
Latency breakdown for phase 0: ["QsBatchToPos: max: 0.254, avg: 0.208", "QsPosToProposal: max: 0.179, avg: 0.165", "ConsensusProposalToOrdered: max: 0.596, avg: 0.555", "ConsensusOrderedToCommit: max: 0.494, avg: 0.467", "ConsensusProposalToCommit: max: 1.074, avg: 1.023"]
Max round gap was 1 [limit 4] at version 1447978. Max no progress secs was 7.128835 [limit 15] at version 1447978.
Test Ok

@@ -160,3 +161,11 @@ proposals:
- FeatureFlag:
enabled:
- zk_id_signature
- name: step_13_start_watching_google_jwks
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

actually could you please move step 7 and 8 to the end (10 and 11) then zkid, then google? so we can control the submittion of those 3 proposals better

@zjma zjma merged commit 7211166 into main Feb 16, 2024
42 of 43 checks passed
@zjma zjma deleted the zjma/release_1_10_jwk_steps_patch branch February 16, 2024 01:31
danielxiangzl added a commit that referenced this pull request Feb 16, 2024
* clean error log lines (#12019)

* [table info][2/4] add utils for table info backup and restore and redesign the db read (#11793)

* separate indexer async v2 db from aptosdb

* address comments

* add utils for table info backup and restore and redesign the db read

* address comments to spawn block sync file ops

* address comments

* tests for events and improve event v1 handling (#12012)

* [move-vm] Cache verified modules (#12002)

* [move-vm] Cache verified modules

* fixup! [move-vm] Cache verified modules

* [passkey] Add MAX_BYTES limit for signatures (#11697)

* [passkey] Add MAX_BYTES limit for signatures

* [passkey] Add tracing for AssertionSignature type and fix README

* [passkey] Rebased on latest main, rerun authenticator_regenerate.sh

* Object Code Deployment module with CLI commands generated (#11748)

* [simple] rename RG split in VmChangeSet flag (#12027)

* rename RG split in VmChangeSet flag

old name was stale, when charging was different

* [fuzzing] fixes oss-fuzz FP and fuzz.sh (#12030)

* [fuzzing] fixes oss-fuzz FP and fuzz.sh

* Update Docker images (#12026)

Co-authored-by: sionescu <sionescu@users.noreply.github.com>

* Update release.yaml (#12020)

* Update release.yaml

* enable REFUNDABLE_BYTES

* enable FairnessShuffler

* enable WEBAUTHN_SIGNATURE

* AIP-54 Object Code Deployment release addition

* enable vtxn and jwk consensus

* Update release.yaml

adding aggregators v2 flags, and updating execution onchain config

* add feature flag for zkID (ZK-only mode)

* fix jwk/zkid entries in release yaml 1.10 (#12024)

* update

* update

* Update release.yaml

fix flag name

* Update release.yaml

rename feature

---------

Co-authored-by: aldenhu <msmouse@gmail.com>
Co-authored-by: hariria <hariria@usc.edu>
Co-authored-by: John Chang <johnchang9094@gmail.com>
Co-authored-by: danielxiangzl <xiangzhuolun@gmail.com>
Co-authored-by: igor-aptos <110557261+igor-aptos@users.noreply.github.com>
Co-authored-by: Alin Tomescu <tomescu.alin@gmail.com>
Co-authored-by: zhoujunma <zjma@users.noreply.github.com>

* Cherry-pick VM changes (#12021)

* [gas] add gas charges for type creation

* [gas-calibration] Add calibration sample

* [move-vm] Implement a per-frame cache for paranoid mode

* fixup! [move-vm] Implement a per-frame cache for paranoid mode

* fixup! fixup! [move-vm] Implement a per-frame cache for paranoid mode

* fixup! fixup! fixup! [move-vm] Implement a per-frame cache for paranoid mode

* fixup! fixup! fixup! fixup! [move-vm] Implement a per-frame cache for paranoid mode

* [gas] add gas charges for dependencies

---------

Co-authored-by: Runtian Zhou <runtian@aptoslabs.com>

* trivial doc fix

* [GHA] Upgrade actions/checkout to v4

* jwk ob counters (#12048)

* Revert "[GHA] Upgrade actions/checkout to v4"

This reverts commit 04d078f.

* [CI][indexer] fix the e2e localnet. (#12047)

* fix the e2e localnet.

* fix the e2e localnet.

* bump latest gas feature version to 14

Also be conservative and leave legacy parameters in >14 versions for
now. Need to clean up after REFUNDABLE_BYTES feature is actually enabled
on all networks.

* compat test to be against the testnet tag

* [GHA] Upgrade lint-test.yaml and the dependent actions to checkout@v4

actions/checkout@v4 doesn't behave well if both a workflow and an
invoked action checkout the source code on top of each other.

* [GHA] Update pin for tj-actions/changed-files

* start jwk consensus for google (#12053)

* [consensus] check rpc epoch in epoch_manager (#12018)

* [consensus] check rpc epoch in epoch_manager

* fix gas version (13 is deprecated/cannot be used) (#12064)

* FatalVMError shouldn't create "Delayed materialization code invariant" (#12044)

* Move all visibility checking into AST-level function_checker, simplify that code a bit, and improve diagnostics. (#11948)

* rust changes to move all visibility checking to AST and clean it up a bit
* change `Known attribute ... position` warning to a neater `Attribute .. position` warning
* add FunctionData id_loc to allow pointing at function name in declaration for more concise error messages. abstract messages a bit in function_checker
* add 'inlined from' labels to diagnostics with labels, fix bug in function_checker to enable post-inlining visibility checking

* lint

* fix for small stakes

* assert

---------

Co-authored-by: igor-aptos <110557261+igor-aptos@users.noreply.github.com>
Co-authored-by: jill <121921928+jillxuu@users.noreply.github.com>
Co-authored-by: George Mitenkov <georgemitenk0v@gmail.com>
Co-authored-by: runtianz <runtian@aptoslabs.com>
Co-authored-by: Andrew Hariri <hariria@usc.edu>
Co-authored-by: John Chang <johnchang9094@gmail.com>
Co-authored-by: Gerardo Di Giacomo <gerardo@aptoslabs.com>
Co-authored-by: sionescu <sionescu@users.noreply.github.com>
Co-authored-by: Junkil Park <jpark@aptoslabs.com>
Co-authored-by: aldenhu <msmouse@gmail.com>
Co-authored-by: danielxiangzl <xiangzhuolun@gmail.com>
Co-authored-by: Alin Tomescu <tomescu.alin@gmail.com>
Co-authored-by: Victor Gao <10379359+vgao1996@users.noreply.github.com>
Co-authored-by: Stelian Ionescu <stelian@aptoslabs.com>
Co-authored-by: Stelian Ionescu <sionescu@cddr.org>
Co-authored-by: larry-aptos <112209412+larry-aptos@users.noreply.github.com>
Co-authored-by: Balaji Arun <balaji@aptoslabs.com>
Co-authored-by: Brian R. Murphy <132495859+brmataptos@users.noreply.github.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants