chore: Merge main into boojum-integration #177
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 ❔ Uses PAT token for release please. <!-- What are the changes this PR brings about? --> <!-- Example: This PR adds a PR template to the repo. --> <!-- (For bigger PRs adding more context is appreciated) --> ## Why ❔ To allow other workflows to be triggered by tags creation. <!-- 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. --> - [x] 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`.
🤖 I have created a release *beep* *boop* --- ## [15.1.1](core-v15.1.0...core-v15.1.1) (2023-10-05) ### Bug Fixes * use gauge instead histogram for replication lag metric ([#159](#159)) ([0d952d4](0d952d4)) --- 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: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com> Co-authored-by: Danil <[email protected]>
# What ❔ * TracerExecutionStatus and TracerExecutionStopReason are part of the ExecutionEndTracer trait, but they were not publicly available. ## Why ❔ * This breaks external implementations of the ExecutionEndTracer
…ry (#134) # What ❔ Replaces container shell with EN and local-env executables in corresponding Docker images to eg. properly handle termination signals. More details in original PR: #76 Courtesy of https://github.com/voron Thanks for the contribution, and sorry it took so long to review - we've been busy with FOSS'ing our repos. ## Why ❔ #76 (comment) ## Checklist - [x] 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`. Co-authored-by: Alex Vorona <[email protected]> Co-authored-by: Roman Brodetski <[email protected]>
…anges (#119) # What ❔ - Enables the Merkle tree to provide proofs for entries. The procedure efficiently handles batched requests. - Allows to verify range proofs using a streaming approach. ## Why ❔ These are preparation steps for snapshot syncing. "Plain" Merkle tree proofs could be used in `eth_getProof` implementation. ## 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`.
# What ❔ - Prettifies Dockerfiles - Removes some unnecessary dependencies on running something outside of Docker build (there are still some, though) ## Why ❔ To make a simple `docker build` command work without any additional hacks ## Checklist <!-- Check your PR fulfills the following items. --> <!-- For draft PRs check the boxes as you complete them. --> - [x] PR title corresponds to the body of PR (we generate changelog entries from PRs). - [ ] 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`. --------- Co-authored-by: Yury Akudovich <[email protected]> Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com> Co-authored-by: Danil <[email protected]> Co-authored-by: Marcin M <[email protected]>
# What ❔ `prover_jobs_fri_l1_batch_number_fkey` is dropped. ## Why ❔ `prover_jobs_fri` is filled only in prover DB, while `l1_batches` -- only in core DB, so we can't have the constraint. ## Checklist <!-- Check your PR fulfills the following items. --> <!-- For draft PRs check the boxes as you complete them. --> - [x] 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`.
ly0va
requested review from
a team,
RomanBrodetski,
perekopskiy,
Deniallugo and
popzxc
as code owners
ly0va
requested review from
yorik,
alexandrst88,
artmakh,
hatemosphere and
otani88
and removed request for
a team
ly0va
changed the title
StanislavBreadless
approved these changes
Oct 9, 2023
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 ❔
Merging main & resolving conflicts
Why ❔
For regenesis
Checklist
zk fmtandzk lint.