forked from aptos-labs/aptos-core
-
Notifications
You must be signed in to change notification settings - Fork 19
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
Monza #1
Merged
Merged
Monza #1
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
* event filter optimization * update * update * lint * nitfix
…ort paths (aptos-labs#11676) - implement exit state analysis - fix ability checker so that it only checks drop on paths that can return
aptos-labs#11629) ### Description Occasionally, the metrics show batches not getting quorum, in forge and testnet. 1. There are false positives (didn't actually expire, only in the metrics), due to batches getting late votes, after they have been committed. This is resolved by caching the committed batches until expiration time; only really really late votes would cause false positives. 2. There are proofs that actually expire without getting quorum. These are written too late into the QS DB; if the entry does not exist in the DB, the vote is discarded, and in some cases more than 33% of votes are actually discarded. This is resolved by writing to the DB in batch_generator, before broadcasting the Batch. In addition the counters for counting proof votes are cleaned up, so the votes/stake are counted on expire time (as originally intended). ### Test Plan Run `realistic_env_max_load_large` and observe that no more proofs fail to get quorum, and metrics look better
* make compatible proto chagne. * format * make compatible proto chagne. * make compatible proto chagne. * make compatible proto chagne. --------- Co-authored-by: Justin Chang <justin@aptoslabs.com>
…esign the db read (aptos-labs#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
* [move-vm] Cache verified modules * fixup! [move-vm] Cache verified modules
* [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
* rename RG split in VmChangeSet flag old name was stale, when charging was different
* [fuzzing] fixes oss-fuzz FP and fuzz.sh
Co-authored-by: sionescu <sionescu@users.noreply.github.com>
* 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 (aptos-labs#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>
* [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>
This reverts commit 04d078f.
* fix the e2e localnet. * fix the e2e localnet.
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.
… of constants (aptos-labs#12518) Some apparently different `ast::Value` values may represent the same runtime values (Value::ByteArray(..) and Value::AddressArray(..) values can each also be represented by Value::Vector(..) instead) and some may not be well-defined at compile time (different symbolic addresses could end up the same).
…os-labs#12545) Reduce the unnecessary transaction metadata instantiation
…2538) with some loadtests we were seeing it reaching 255
add check for recursive struct definitions on AST
Co-authored-by: ibalajiarun <3034228+ibalajiarun@users.noreply.github.com>
…tions (aptos-labs#12420) * disable X::set() release builder update for randomness framework (aptos-labs#12381) print jwk configs in release builder maybe keep the gas schedule update function fix tests using version_set_version fix doc test fixing test_register_and_update_validator fixing tests using consensus_config::set fixing storage_integration_test update spec also disable gas update function (aptos-labs#12431) * still have to disable gas function * update fix doc Co-authored-by: Greg Nazario <greg@gnazar.io> update update rename function update spec change_feature_flags_for_testing/verification (aptos-labs#12506) * change_feature_flags_for_testing/verification * update features function usage in genesis * update features function usage in harness * debug * update remaining reference in e2e-move-tests * a tmp release entry for randomness framework upgrade fix generate-proposals update release yaml for randomness framework (aptos-labs#12523) * debug * debug * debug * debug * debug * fix spec * update doc * update * update * support release entries for randomness config and jwk consensus config * update * lint
This reduces memory footprint of amortized usage of delayed field with a single version from 3000 bytes to 600 bytes per delayed field. Basically BTreeMap stores things in vectors of 5, and size of the value is large. This invalidates BTreeMap's cache optimization of storing them all together.
We currently dont check that the tag and the aptos-node cargo.toml version match This ensures that before publish we have to check the tag and version match only for release images Test Plan: wrote unittests and added a testing workflow made the script possibel to unittest
* Reduce mempool poll time to 10ms * Minor fix * Rust lint * Reset #validators to 20 for forge * Change forge parameters * Reverting forge changes
…12583) temporarily, until gas charges for aggregator loading are implemented, limit number of aggregators per resource
* fix * Revert "fix" This reverts commit 50c9b5d. * fix in exp_builder * rebase
add check for cyclic type instantiations for compiler v2 on the ast level
0xmovses
pushed a commit
that referenced
this pull request
Apr 8, 2024
* jwk types update * update * update * jwk txn and execution * update * fix dummy * update * update * update * update * update * update * remove dummy txns * check voting power than verify signature * fix warnings * update * update QuorumCertifiedUpdate struct
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.
Description
Test Plan