chore: Merge main to kl factory #1759
Merged
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
## What ❔ fixes LegacyCall: subcalls should be of type LegacyCall. adds bincode deserialization tests ## Why ❔ Fix LegacyCall deserialization ## Checklist <!-- Check your PR fulfills the following items. --> <!-- For draft PRs check the boxes as you complete them. --> - [ ] PR title corresponds to the body of PR (we generate changelog entries from PRs). - [ ] Tests for the changes have been added / updated. - [ ] Documentation comments have been added / updated. - [ ] Code has been formatted via `zk fmt` and `zk lint`. - [ ] Spellcheck has been run via `zk spellcheck`. - [ ] Linkcheck has been run via `zk linkcheck`.
## What ❔ Remove mentions of the `storage` table in the codebase. ## Why ❔ The table has been deprecated for some time and should eventually be removed. ## Checklist - [x] PR title corresponds to the body of PR (we generate changelog entries from PRs). - [x] Tests for the changes have been added / updated. - [x] Code has been formatted via `zk fmt` and `zk lint`. - [x] Spellcheck has been run via `zk spellcheck`. - [ ] Linkcheck has been run via `zk linkcheck`.
## What ❔ Renames "miniblock" to "L2 block" in libraries (i.e., `core/lib` crates with the exception of `zksync_core`). ## Why ❔ See #1696 for reasoning. ## Checklist - [x] PR title corresponds to the body of PR (we generate changelog entries from PRs). - [x] Tests for the changes have been added / updated. - [x] Documentation comments have been added / updated. - [x] Code has been formatted via `zk fmt` and `zk lint`. - [x] Spellcheck has been run via `zk spellcheck`. - [x] Linkcheck has been run via `zk linkcheck`.
## What ❔ Logs and exposes as gauges latency of recovery stages (Postgres, Merkle tree, state keeper). ## Why ❔ Necessary for monitoring recovery performance. ## Checklist - [x] PR title corresponds to the body of PR (we generate changelog entries from PRs). - [x] Tests for the changes have been added / updated. - [x] Documentation comments have been added / updated. - [x] Code has been formatted via `zk fmt` and `zk lint`. - [x] Spellcheck has been run via `zk spellcheck`. - [x] Linkcheck has been run via `zk linkcheck`.
…on (#1753) ## What ❔ Adds `enum_index_migration_cursor` back to storage layout description and says it's deprecated. ## Why ❔ Storage layout should be complete ## Checklist <!-- Check your PR fulfills the following items. --> <!-- For draft PRs check the boxes as you complete them. --> - [ ] PR title corresponds to the body of PR (we generate changelog entries from PRs). - [ ] Tests for the changes have been added / updated. - [ ] Documentation comments have been added / updated. - [ ] Code has been formatted via `zk fmt` and `zk lint`. - [ ] Spellcheck has been run via `zk spellcheck`. - [ ] Linkcheck has been run via `zk linkcheck`.
## What ❔ Fixes recently discovered bug in v22.1.0 where executor and fee migration logic get starved out by async catch up task that holds a long-term connection. ## Why ❔ <!-- Why are these changes done? What goal do they contribute to? What are the principles behind them? --> <!-- Example: PR templates ensure PR reviewers, observers, and future iterators are in context about the evolution of repos. --> ## Checklist <!-- Check your PR fulfills the following items. --> <!-- For draft PRs check the boxes as you complete them. --> - [ ] PR title corresponds to the body of PR (we generate changelog entries from PRs). - [ ] Tests for the changes have been added / updated. - [ ] Documentation comments have been added / updated. - [ ] Code has been formatted via `zk fmt` and `zk lint`. - [ ] Spellcheck has been run via `zk spellcheck`. - [ ] Linkcheck has been run via `zk linkcheck`.
🤖 I have created a release *beep* *boop* --- ## [13.0.0](prover-v12.2.0...prover-v13.0.0) (2024-04-22) ### ⚠ BREAKING CHANGES * **vm:** 1 5 0 support ([#1508](#1508)) ### Features * Archive old prover jobs ([#1516](#1516)) ([201476c](201476c)) * Archiving of prover in gpu_prover_queue ([#1537](#1537)) ([a970629](a970629)) * **configs:** Implement new format of configs and implement protobuf for it ([#1501](#1501)) ([086ba5b](086ba5b)) * **db:** Wrap sqlx errors in DAL ([#1522](#1522)) ([6e9ed8c](6e9ed8c)) * fix availability checker ([#1574](#1574)) ([b2f21fb](b2f21fb)) * Prover CLI Scaffoldings ([#1609](#1609)) ([9a22fa0](9a22fa0)) * Remove zksync-rs SDK ([#1559](#1559)) ([cc78e1d](cc78e1d)) * **sqlx:** Use offline mode by default ([#1539](#1539)) ([af01edd](af01edd)) * **vm:** 1 5 0 support ([#1508](#1508)) ([a6ccd25](a6ccd25)) ### Bug Fixes * **en:** Fix miscellaneous snapshot recovery nits ([#1701](#1701)) ([13bfecc](13bfecc)) * made consensus store certificates asynchronously from statekeeper ([#1711](#1711)) ([d1032ab](d1032ab)) ### Performance Improvements * **merkle tree:** Manage indices / filters in RocksDB ([#1550](#1550)) ([6bbfa06](6bbfa06)) ### Reverts * **env:** Remove `ZKSYNC_HOME` env var from server ([#1713](#1713)) ([aed23e1](aed23e1)) --- This PR was generated with [Release Please](https://github.com/googleapis/release-please). See [documentation](https://github.com/googleapis/release-please#release-please). Co-authored-by: perekopskiy <53865202+perekopskiy@users.noreply.github.com>
🤖 I have created a release *beep* *boop* --- ## [23.1.0](core-v23.0.0...core-v23.1.0) (2024-04-22) ### Features * **en:** Add boxed L2 client and use it in DI ([#1627](#1627)) ([9948187](9948187)) * Extract block_reverter into separate crate ([#1632](#1632)) ([8ab2488](8ab2488)) * Extract house keeper into separate crate ([#1685](#1685)) ([f6f49b7](f6f49b7)) * remove enum index migration ([#1734](#1734)) ([13c0f52](13c0f52)) * **state-keeper:** miniblock max payload size (BFT-417) ([#1284](#1284)) ([a3c8e81](a3c8e81)) ### Bug Fixes * **en:** Fix miscellaneous snapshot recovery nits ([#1701](#1701)) ([13bfecc](13bfecc)) * ensure two connections for both executor and async catchup ([#1755](#1755)) ([3b14a9f](3b14a9f)) * made consensus store certificates asynchronously from statekeeper ([#1711](#1711)) ([d1032ab](d1032ab)) * **merkle_tree:** don't panic in `BlockOutputWithProofs::verify_proofs` ([#1717](#1717)) ([a44fac9](a44fac9)) * **types:** fix LegacyCall type ([#1739](#1739)) ([712919f](712919f)) ### Performance Improvements * **en:** Monitor recovery latency by stage ([#1725](#1725)) ([d7efdd5](d7efdd5)) ### Reverts * **env:** Remove `ZKSYNC_HOME` env var from server ([#1713](#1713)) ([aed23e1](aed23e1)) --- This PR was generated with [Release Please](https://github.com/googleapis/release-please). See [documentation](https://github.com/googleapis/release-please#release-please). --------- Co-authored-by: perekopskiy <mikeson.dp@gmail.com> Co-authored-by: perekopskiy <53865202+perekopskiy@users.noreply.github.com>
## What ❔ Allows configuring max response size per method for JSON-RPC web servers. ## Why ❔ Makes EN more operator-friendly. Some RPC methods (e.g., `eth_getTransactionReceipt`) may return large responses, while for others, smaller output size is OK. ## Checklist - [x] PR title corresponds to the body of PR (we generate changelog entries from PRs). - [x] Tests for the changes have been added / updated. - [x] Documentation comments have been added / updated. - [x] Code has been formatted via `zk fmt` and `zk lint`. - [x] Spellcheck has been run via `zk spellcheck`. - [x] Linkcheck has been run via `zk linkcheck`.
StanislavBreadless
requested review from
RomanBrodetski,
perekopskiy,
Deniallugo and
popzxc
as code owners
StanislavBreadless
changed the title
kelemeno
approved these changes
Apr 22, 2024
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.
What ❔
Why ❔
Checklist
zk fmtandzk lint.zk spellcheck.zk linkcheck.