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: Prover CLI Scaffoldings #1609

Merged
merged 10 commits into from Apr 11, 2024
Merged

feat: Prover CLI Scaffoldings #1609

merged 10 commits into from Apr 11, 2024

Conversation

ColoCarletti
Copy link
Contributor

@ColoCarletti ColoCarletti commented Apr 8, 2024

What ❔

This PR implements the scaffolding for a CLI to interact with the prover. Additionally, it integrates the functionality of the tool crate.

Why ❔

The purpose of this CLI is to simplify the process of interacting with the prover and enhance its usability. Users can easily interact with the prover without requiring specialized insider knowledge, ensuring that it can managed without direct database access and complex manual queries.

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.
  • Linkcheck has been run via zk linkcheck.

@ilitteri ilitteri changed the title feat: prover cli feat: Prover CLI Scaffoldings Apr 9, 2024
@ColoCarletti ColoCarletti marked this pull request as ready for review April 9, 2024 21:52
Copy link
Member

@ilitteri ilitteri left a comment

Choose a reason for hiding this comment

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

LGTM

Copy link
Contributor

@EmilLuta EmilLuta left a comment

Choose a reason for hiding this comment

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

LGTM. Whilst outside the scope of this PR, I'd suggest we slowly start adding tests over it. It's much easier to integrate at the start, than midway through.

@EmilLuta
Copy link
Contributor

I also noticed that protobuf compatibility is breaking. That's a new job, might've been a fluke. Restarted. If it doesn't pass, we may need to dive deeper there.

@Artemka374
Copy link
Contributor

@EmilLuta Sometimes you need just to merge main, I think it is comparing protobuf configs from there

Copy link
Contributor

@Artemka374 Artemka374 left a comment

Choose a reason for hiding this comment

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

LGTM

@Artemka374 Artemka374 added this pull request to the merge queue Apr 11, 2024
Merged via the queue into main with commit 9a22fa0 Apr 11, 2024
25 checks passed
@Artemka374 Artemka374 deleted the feat_prover_cli branch April 11, 2024 14:37
github-merge-queue bot pushed a commit that referenced this pull request Apr 22, 2024
🤖 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>
Comment on lines +13 to +15
tokio = { version = "1", features = ["rt-multi-thread", "macros"] }
env_logger = "0.10"
log = "0.4"
Copy link
Member

Choose a reason for hiding this comment

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

  1. Is there a reason not to use workspace deps here?
  2. Why do we need env_logger and log when we use tracing and vlog (or tracing-subscriber, if you have to) now?

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

5 participants