Skip to content

Conversation

@colinlyguo
Copy link
Contributor

@colinlyguo colinlyguo commented May 26, 2025

Purpose or design rationale of this PR

euclid verifier won't be initialized, thus removing loadOpenVMVks as well because it will call euclid verifier's dump_vk function.

PR title

Your PR title must follow conventional commits (as we are doing squash merge for each PR), so it must start with one of the following types:

  • fix: A bug fix

Deployment tag versioning

Has tag in common/version.go been updated or have you added bump-version label to this PR?

  • Yes

Breaking change label

Does this PR have the breaking-change label?

  • No, this PR is not a breaking change

Summary by CodeRabbit

  • Chores

    • Updated version to v4.5.19.
  • Refactor

    • Removed references to the "euclid" fork and updated related documentation to use explicit fork names.
    • Streamlined initialization by discontinuing the loading of verification keys for the "euclid" fork.

@colinlyguo colinlyguo requested review from georgehao and zimpha May 26, 2025 07:29
@coderabbitai
Copy link

coderabbitai bot commented May 26, 2025

Walkthrough

This change removes the EuclidFork constant and all associated references from the codebase, updates comments to use explicit string literals for fork names, and increments the version number from v4.5.18 to v4.5.19. Loading of OpenVM verification keys for the deprecated fork is also eliminated.

Changes

File(s) Change Summary
common/types/message/message.go Removed EuclidFork constant; updated comments to use "euclidv1" and "euclidv2" string literals.
coordinator/internal/logic/verifier/verifier.go Removed loading of OpenVM verification keys for the EuclidFork fork in NewVerifier.
common/version/version.go Updated version tag from v4.5.18 to v4.5.19.

Sequence Diagram(s)

sequenceDiagram
    participant Coordinator
    participant Verifier

    Coordinator->>Verifier: NewVerifier()
    Note right of Verifier: Loads OpenVM Vks for "euclidv2" only
Loading

Possibly related PRs

  • refactor(coordinator): remove outdated logic #1668: Both PRs remove references and logic related to the outdated EuclidFork verifier, including the removal of constants and the disabling of loading verification keys for the euclid fork, indicating they address the same deprecated verifier code.

Suggested labels

bump-version

Suggested reviewers

  • noel2004
  • yiweichi

Poem

A fork once called Euclid, now gone from our sight,
With constants and keys, we tidied up right.
The version hops forward, a neat little fix,
As code bunnies hop through their usual tricks.
🐇✨

Warning

There were issues while running some tools. Please review the errors and either fix the tool's configuration or disable the tool if it's a critical failure.

🔧 golangci-lint (1.64.8)

level=warning msg="[runner] Can't run linter goanalysis_metalinter: buildir: failed to load package zstd: could not load export data: no export data for "github.com/scroll-tech/da-codec/encoding/zstd""
level=error msg="Running error: can't run linter goanalysis_metalinter\nbuildir: failed to load package zstd: could not load export data: no export data for "github.com/scroll-tech/da-codec/encoding/zstd""

✨ Finishing Touches
  • 📝 Generate Docstrings

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share
🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

  • Review comments: Directly reply to a review comment made by CodeRabbit. Example:
    • I pushed a fix in commit <commit_id>, please review it.
    • Explain this complex logic.
    • Open a follow-up GitHub issue for this discussion.
  • Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
    • @coderabbitai explain this code block.
    • @coderabbitai modularize this function.
  • PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
    • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
    • @coderabbitai read src/utils.ts and explain its main purpose.
    • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
    • @coderabbitai help me debug CodeRabbit configuration file.

Support

Need help? Create a ticket on our support page for assistance with any issues or questions.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

  • @coderabbitai pause to pause the reviews on a PR.
  • @coderabbitai resume to resume the paused reviews.
  • @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
  • @coderabbitai full review to do a full review from scratch and review all the files again.
  • @coderabbitai summary to regenerate the summary of the PR.
  • @coderabbitai generate docstrings to generate docstrings for this PR.
  • @coderabbitai generate sequence diagram to generate a sequence diagram of the changes in this PR.
  • @coderabbitai resolve resolve all the CodeRabbit review comments.
  • @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
  • @coderabbitai help to get help.

Other keywords and placeholders

  • Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
  • Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
  • Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

  • You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
  • Please see the configuration documentation for more information.
  • If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

  • Visit our Documentation for detailed information on how to use CodeRabbit.
  • Join our Discord Community to get help, request features, and share feedback.
  • Follow us on X/Twitter for updates and announcements.

@codecov-commenter
Copy link

codecov-commenter commented May 26, 2025

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 40.96%. Comparing base (a55c7bd) to head (4f5d3c6).

Additional details and impacted files
@@             Coverage Diff             @@
##           develop    #1669      +/-   ##
===========================================
+ Coverage    40.94%   40.96%   +0.01%     
===========================================
  Files          225      225              
  Lines        18071    18071              
===========================================
+ Hits          7399     7402       +3     
+ Misses        9950     9948       -2     
+ Partials       722      721       -1     
Flag Coverage Δ
common 29.86% <ø> (ø)
coordinator 34.55% <ø> (+0.09%) ⬆️
database 42.05% <ø> (ø)
rollup 49.82% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

Copy link

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

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

Actionable comments posted: 1

🧹 Nitpick comments (2)
common/types/message/message.go (2)

99-100: Apply the same constant-based approach for BatchTaskDetail.

The ForkName field comment here also relies on the literal "euclidv1". For consistency and to prevent typos, define and reference a constant EuclidV1ForkNameForProver instead of a raw string.

-// use one of the string of "euclidv1" / "euclidv2"
+// use one of the string of EuclidV1ForkNameForProver / EuclidV2ForkNameForProver

112-113: Mirror the refactor in BundleTaskDetail.

Again, switch from the raw "euclidv1" literal to a shared constant for improved maintainability.

-// use one of the string of "euclidv1" / "euclidv2"
+// use one of the string of EuclidV1ForkNameForProver / EuclidV2ForkNameForProver
📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between a55c7bd and 4f5d3c6.

📒 Files selected for processing (3)
  • common/types/message/message.go (3 hunks)
  • common/version/version.go (1 hunks)
  • coordinator/internal/logic/verifier/verifier.go (0 hunks)
💤 Files with no reviewable changes (1)
  • coordinator/internal/logic/verifier/verifier.go
⏰ Context from checks skipped due to timeout of 90000ms (3)
  • GitHub Check: tests
  • GitHub Check: tests
  • GitHub Check: tests
🔇 Additional comments (1)
common/version/version.go (1)

8-8:

Details

✅ Verification successful

Approve version bump to v4.5.19.

Updating the tag to "v4.5.19" aligns with the PR’s release plan. Ensure no leftover references to the old version remain elsewhere in the repo.

To confirm cleanup:


🏁 Script executed:

#!/bin/bash
rg -n "v4.5.18"

Length of output: 15


To ensure we didn’t miss any literal occurrences of the old tag, let’s search using exact-string matches:


🏁 Script executed:

#!/bin/bash
# Look for any exact matches of the previous version
rg -F -n "v4.5.18"
rg -F -n "4.5.18"

Length of output: 36


Approved version bump to v4.5.19

Ran exact‐string searches for v4.5.18 and 4.5.18—no matches found. No leftover references to the old version remain.

@colinlyguo colinlyguo merged commit f824fb0 into develop May 26, 2025
15 checks passed
@colinlyguo colinlyguo deleted the fix-coordinator-new-verifier branch May 26, 2025 07:42
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.

5 participants