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

feat(vm): Support tracers for old vm #926

Merged
merged 3 commits into from
Jan 25, 2024
Merged

Conversation

Deniallugo
Copy link
Contributor

What ❔

Support existing tracers for old vms

Why ❔

First step for making tracing on flight instead of saving it in db

Checklist

  • 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.

Signed-off-by: Danil <deniallugo@gmail.com>
Signed-off-by: Danil <deniallugo@gmail.com>
Signed-off-by: Danil <deniallugo@gmail.com>
@Deniallugo Deniallugo force-pushed the deniallugo-support-old-tracers branch from 665ce91 to e3d27b5 Compare January 23, 2024 18:17
@Deniallugo Deniallugo requested review from perekopskiy and RomanBrodetski and removed request for RomanBrodetski January 23, 2024 18:19
Copy link
Contributor

@perekopskiy perekopskiy left a comment

Choose a reason for hiding this comment

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

What about VM m5?

@Deniallugo
Copy link
Contributor Author

What about VM m5?

@perekopskiy VM m5 was before full launch and there are only ~300 batches with m5, we decided to not implement tracers for them

@Deniallugo Deniallugo added this pull request to the merge queue Jan 25, 2024
Merged via the queue into main with commit 9fc2d95 Jan 25, 2024
27 checks passed
@Deniallugo Deniallugo deleted the deniallugo-support-old-tracers branch January 25, 2024 10:25
github-merge-queue bot pushed a commit that referenced this pull request Jan 30, 2024
🤖 I have created a release *beep* *boop*
---


##
[20.2.0](core-v20.1.0...core-v20.2.0)
(2024-01-30)


### Features

* added unauthenticated version of gcs object store
([#916](#916))
([638a813](638a813))
* Adding EN snapshots applier
([#882](#882))
([0d2ba09](0d2ba09))
* consensus component config for main node and external node
([#881](#881))
([1aed8de](1aed8de))
* **en:** Make ENs detect reorgs earlier
([#964](#964))
([b043cc8](b043cc8))
* **en:** Restore state keeper storage from snapshot
([#885](#885))
([a9553b5](a9553b5))
* protobuf-generated json configs for the main node (BFT-371)
([#458](#458))
([f938314](f938314))
* Remove zkevm_test_harness public reexport from zksync_types
([#929](#929))
([dd1a35e](dd1a35e))
* **state-keeper:** track the time that individual transactions spend in
mempool ([#941](#941))
([fa45aa9](fa45aa9))
* **vm:** detailed circuit statistic
([#845](#845))
([a20af60](a20af60))
* **vm:** Support tracers for old vm
([#926](#926))
([9fc2d95](9fc2d95))


### Bug Fixes

* **api:** Order transaction traces in `debug_traceBlock*` methods
([#924](#924))
([5918ef9](5918ef9))
* **db:** Make `get_expected_l1_batch_timestamp()` more efficient
([#963](#963))
([7334679](7334679))
* **db:** Make `snapshot_recovery` migration backward-compatible
([#961](#961))
([e756762](e756762))
* **zksync_types:** Update SerializationTransactionError::OversizedData
description
([#949](#949))
([c95f3ee](c95f3ee))

---
This PR was generated with [Release
Please](https://github.com/googleapis/release-please). See
[documentation](https://github.com/googleapis/release-please#release-please).
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.

None yet

2 participants