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

chore: bump proto #153

Open
wants to merge 6 commits into
base: main
Choose a base branch
from
Open

chore: bump proto #153

wants to merge 6 commits into from

Conversation

Vritra4
Copy link
Contributor

@Vritra4 Vritra4 commented Feb 3, 2025

Description

Closes: #XXXX

This PR is interim and should not be tagged since it has dependency on kvindexer's non-tagged commit
I'll make another PR with tagged kvindexer(depend on this merge commit) once this PR merged to main.
I think we can make a tag minievm once another PR I mentioned


Author Checklist

All items are required. Please add a note to the item if the item is not applicable and
please add links to any relevant follow up issues.

I have...

  • included the correct type prefix in the PR title, you can find examples of the prefixes below:
  • confirmed ! in the type prefix if API or client breaking change
  • targeted the correct branch
  • provided a link to the relevant issue or specification
  • reviewed "Files changed" and left comments if necessary
  • included the necessary unit and integration tests
  • updated the relevant documentation or specification, including comments for documenting Go code
  • confirmed all CI checks have passed

Reviewers Checklist

All items are required. Please add a note if the item is not applicable and please add
your handle next to the items reviewed if you only reviewed selected items.

I have...

  • confirmed the correct type prefix in the PR title
  • confirmed all author checklist items have been addressed
  • reviewed state machine logic, API design and naming, documentation is accurate, tests and test coverage

Summary by CodeRabbit

  • Chores
    • Refined our CI workflow to optimize maintenance checks by excluding swagger-ui.css from spell-checking.
    • Upgraded Docker build environments with newer base images for improved performance.
    • Updated core dependencies and toolchain versions to enhance compatibility and stability.
    • Streamlined internal error handling by removing the home path check in the export process and cleaned up code annotations for smoother operations.

@Vritra4 Vritra4 requested a review from beer-1 February 3, 2025 03:25
@Vritra4 Vritra4 requested a review from a team as a code owner February 3, 2025 03:25
Copy link

coderabbitai bot commented Feb 3, 2025

Walkthrough

This pull request introduces a set of configuration and dependency updates across the repository. The changes include modifying the GitHub Actions spellcheck job to skip an additional file, updating Docker base images, bumping a proto version in the Makefile, and streamlining some application code comments. Additionally, several Go module dependencies and toolchain versions have been upgraded or adjusted, and the protocol buffers configuration has been revised.

Changes

File(s) Change Summary
.github/workflows/spellcheck.yml Added swagger-ui.css to the exclusion list for the codespell check.
Dockerfile, Dockerfile.arm64 Upgraded the Go builder base images from Go 1.22 to 1.23 while retaining the underlying OS version.
Makefile Updated protoVer from 0.14.0 to 0.15.3, affecting the protobuf image naming.
app/app.go, cmd/minitiad/root.go Removed redundant comments in variable declarations in app/app.go and eliminated an error check for a missing homePath in the appExport method in cmd/minitiad/root.go.
go.mod, integration-tests/go.mod Upgraded Go version and toolchain; updated dependency versions (e.g., kvindexer and its submodules) and downgraded github.com/gogo/protobuf; removed the minievm dependency from integration tests.
proto/buf.yaml Removed explicit commit hashes from several dependencies and added the new dependency buf.build/protocolbuffers/wellknowntypes:v23.4 while generalizing version references for others.

Sequence Diagram(s)

sequenceDiagram
    participant User
    participant appCreator
    participant initiaApp

    User->>appCreator: Invoke appExport(...)
    Note over appCreator: (Previously: check for homePath)
    appCreator->>initiaApp: Instantiate application
    appCreator->>initiaApp: Export state & validators
    initiaApp-->>appCreator: Export confirmation
    appCreator-->>User: Provide export data
Loading

Possibly related PRs

  • bump: cometbft to add more invalid block checker #131: The changes in the main PR, which involve updating the go.mod file to reflect a new Go version and various dependency updates, are related to the retrieved PR's modifications to the go.mod file, which also includes updates to the Go version and dependency management.
  • chore: use kvindexr which ignores cache error #94: The changes in the main PR, which involve updating the go.mod file to reflect a new version of the kvindexer dependency, are directly related to the retrieved PR that also updates the kvindexer dependency version, indicating a shared focus on dependency management.
  • chore: add spellcheck and run #111: The changes in the main PR, which involve modifying the spellcheck job in the GitHub Actions workflow to exclude swagger-ui.css, are related to the retrieved PR that introduces a new spellcheck workflow, as both pertain to the implementation and configuration of spell-checking processes in the project.

Suggested reviewers

  • beer-1

Poem

I'm a bunny coding through the night,
Hopping over bugs with all my might.
Docker and Go, a tasty treat,
Dependencies updated, oh so neat!
With leaps of joy, I celebrate this flight.
Happy coding, may your commits be light!
🐰🥕


📜 Recent review details

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

📥 Commits

Reviewing files that changed from the base of the PR and between b2d9832 and 23c0bdb.

📒 Files selected for processing (1)
  • proto/buf.yaml (1 hunks)
🧰 Additional context used
🪛 Gitleaks (8.21.2)
proto/buf.yaml

8-8: Detected a Generic API Key, potentially exposing access to various services and sensitive operations.

(generic-api-key)

⏰ Context from checks skipped due to timeout of 90000ms (4)
  • GitHub Check: golangci-lint
  • GitHub Check: Run test and upload codecov
  • GitHub Check: Minitiad
  • GitHub Check: Analyze (go)
🔇 Additional comments (3)
proto/buf.yaml (3)

7-7: Commit Hash Update for cosmos/gogo-proto

The dependency for buf.build/cosmos/gogo-proto has been updated with the commit hash cc916c31859748a68fd229a3c8d7a2e8. Please verify that this commit hash is accurate, intended, and maintains compatibility with the rest of the protobuf-related dependencies.


11-11: Addition of the wellknowntypes Dependency

The new dependency buf.build/protocolbuffers/wellknowntypes:v23.4 has been added. Ensure that this version aligns with other dependency constraints (e.g., changes in go.mod regarding protobuf versions) and does not introduce conflicts.


8-8: Static Analysis: Review for Potential False Positive

Static analysis reported a potential generic API key on line 8 (buf.build/googleapis/googleapis:cc916c31859748a68fd229a3c8d7a2e8). Assuming this value is simply a commit hash used for versioning, please verify that it is not exposing any sensitive credentials.

🧰 Tools
🪛 Gitleaks (8.21.2)

8-8: Detected a Generic API Key, potentially exposing access to various services and sensitive operations.

(generic-api-key)


🪧 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.
    • Generate unit testing code for this file.
    • 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 generate unit testing code for this file.
    • @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 generate unit testing code.
    • @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.

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. (Beta)
  • @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.

proto/buf.yaml Show resolved Hide resolved
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: 0

🧹 Nitpick comments (1)
go.mod (1)

275-276: Commented Replace Directive for gogo/protobuf

The replace directives for github.com/gogo/protobuf have been commented out on lines 275-276. Verify if this block is meant to be retained for reference or eventually removed. If it is no longer needed, consider cleaning it up to avoid confusion.

📜 Review details

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

📥 Commits

Reviewing files that changed from the base of the PR and between 4b29d9b and 869ab1f.

⛔ Files ignored due to path filters (5)
  • go.sum is excluded by !**/*.sum
  • go.work is excluded by !**/*.work
  • integration-tests/go.sum is excluded by !**/*.sum
  • x/evm/types/query.pb.go is excluded by !**/*.pb.go
  • x/evm/types/tx.pb.go is excluded by !**/*.pb.go
📒 Files selected for processing (9)
  • .github/workflows/spellcheck.yml (1 hunks)
  • Dockerfile (1 hunks)
  • Dockerfile.arm64 (1 hunks)
  • Makefile (1 hunks)
  • app/app.go (1 hunks)
  • cmd/minitiad/root.go (0 hunks)
  • go.mod (4 hunks)
  • integration-tests/go.mod (2 hunks)
  • proto/buf.yaml (1 hunks)
💤 Files with no reviewable changes (1)
  • cmd/minitiad/root.go
✅ Files skipped from review due to trivial changes (3)
  • Makefile
  • Dockerfile
  • app/app.go
⏰ Context from checks skipped due to timeout of 90000ms (1)
  • GitHub Check: Run test and upload codecov
🔇 Additional comments (7)
Dockerfile.arm64 (1)

1-1: Base Image Update Verification

The base image on line 1 is updated to arm64v8/golang:1.23-bullseye, which is consistent with the overall upgrade to Go 1.23 used elsewhere in the project. Please confirm that all build scripts and dependency versions are compatible with this new image.

proto/buf.yaml (2)

6-8: Dependency Version Flexibility Update

The dependency entries for buf.build/cosmos/cosmos-proto, buf.build/cosmos/gogo-proto, and buf.build/googleapis/googleapis have been updated to remove hard-coded commit hashes. This change introduces flexibility in selecting versions, but please verify that downstream code remains compatible with any new versions that the dependency resolver might pull.


11-11: New Dependency Addition

A new dependency buf.build/protocolbuffers/wellknowntypes:v23.4 has been added. Ensure that this version (v23.4) integrates correctly with the protobuf definitions used across the project.

.github/workflows/spellcheck.yml (1)

16-16: Expanded Skip List for Spellcheck

The addition of swagger-ui.css to the skip list on line 16 is appropriate if this file is auto-generated or maintained separately. This change will help reduce noise in the spellcheck results.

integration-tests/go.mod (1)

3-5: Go Version and Toolchain Upgrade

The Go version has been updated to 1.23.3 and the toolchain to go1.23.5 as shown on lines 3 and 5. This aligns the integration tests module with the main project’s configuration. Please double-check that all integration tests run as expected with these new versions.

go.mod (2)

3-5: Main Module Go Version and Toolchain Update

The main module’s Go version and toolchain have been updated to 1.23.3 and go1.23.5 respectively. This ensures consistency across the codebase.


41-45: KV Indexer Dependency Bump

The version for github.com/initia-labs/kvindexer and its submodules (block, evm-nft, evm-tx, and pair) have been bumped to new pre-release versions. This update appears to follow the required interim changes. Please ensure that all components using these modules have been tested against these new versions.

Copy link

codecov bot commented Feb 3, 2025

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 57.34%. Comparing base (703e4d7) to head (23c0bdb).
Report is 2 commits behind head on main.

Additional details and impacted files

Impacted file tree graph

@@           Coverage Diff           @@
##             main     #153   +/-   ##
=======================================
  Coverage   57.34%   57.34%           
=======================================
  Files         113      113           
  Lines       10629    10629           
=======================================
  Hits         6095     6095           
  Misses       3649     3649           
  Partials      885      885           
Files with missing lines Coverage Δ
app/app.go 58.18% <ø> (ø)

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.

2 participants