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

fix proto-gen after ibc v6.3.x upgrade #1499

Merged
merged 2 commits into from
Apr 26, 2024
Merged

fix proto-gen after ibc v6.3.x upgrade #1499

merged 2 commits into from
Apr 26, 2024

Conversation

joe-bowman
Copy link
Contributor

@joe-bowman joe-bowman commented Apr 25, 2024

1. Summary

Fixes make proto-gen post ibc-go upgrade.

We use buf for generating protobuf files.

The definitions pushed to buf by the ibc-go team are incorrect, and use the v8+ file path, with just the version changed to v6, causing all proto-gen attempts to fail.

I published to buf.build/joe-bowman/ibc the v6.3.1 protobuf definitions, updated buf.yaml, recreated the lockfile and now make proto-gen runs sweetly.

  • Also bumped buf, and ibc-go to v6.3.1, ics23 to 0.9.1 and cometbft-db to v0.12.0.

Summary by CodeRabbit

  • Chores
    • Updated BUF_VERSION to 1.31.0 to ensure compatibility and performance improvements.
  • Documentation
    • Improved formatting and clarity in the README, including adjustments to text alignment and content readability.
  • Refactor
    • Upgraded the base image in Dockerfile to golang:1.22.2-alpine3.19 for enhanced security and stability.

Copy link

vercel bot commented Apr 25, 2024

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name Status Preview Comments Updated (UTC)
quicksilver ✅ Ready (Inspect) Visit Preview 💬 Add feedback Apr 25, 2024 11:06pm

Copy link
Contributor

coderabbitai bot commented Apr 25, 2024

Important

Auto Review Skipped

Review was skipped due to path filters

Files ignored due to path filters (2)
  • icq-relayer/go.mod is excluded by !**/*.mod, !**/*.mod
  • icq-relayer/go.sum is excluded by !**/*.sum, !**/*.sum

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Walkthrough

This update brings a version bump in the Makefile for BUF, minor formatting refinements in the README.md for better readability and clarity, and a Dockerfile adjustment that updates the base image to a newer Alpine version. These changes enhance tool compatibility and improve documentation presentation.

Changes

File Change Summary
Makefile Updated BUF_VERSION from 1.30.1 to 1.31.0.
README.md Minor formatting adjustments and text clarity improvements in system requirements and software dependencies.
proto/.../Dockerfile Updated base image from golang:1.22.2-alpine3.18 to golang:1.22.2-alpine3.19.

Poem

🐰🎉

Hopping through the code, with a tiny tweak,
I changed a version, made the future less bleak.
A nudge in the Dockerfile, a format so sleek,
Now the README shines, no longer meek!
Celebrate the changes, for progress we seek! 🌟

🐰🎉


Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?

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>.
    • 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 generate interesting stats about this repository and render them as a table.
    • @coderabbitai show all the console.log statements in this repository.
    • @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.

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 as PR comments)

  • @coderabbitai pause to pause the reviews on a PR.
  • @coderabbitai resume to resume the paused reviews.
  • @coderabbitai review to trigger a review. This is useful when automatic reviews are disabled for the repository.
  • @coderabbitai resolve resolve all the CodeRabbit review comments.
  • @coderabbitai help to get help.

Additionally, you can add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.

CodeRabbit Configration 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.

Copy link
Contributor

@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

Out of diff range and nitpick comments (4)
README.md (4)

Line range hint 11-11: Consider adding a possessive apostrophe: "users' voting rights."

- stripping away users voting rights
+ stripping away users' voting rights

This change will correct the grammar, making the sentence clearer and more professional.


Line range hint 12-12: Consider using American English for consistency: "incentivize" and "decentralization."

- incentivise decentralisation
+ incentivize decentralization

This change aligns the spelling with American English, which is typically used in technical documentation, enhancing consistency across the document.


Line range hint 54-54: Consider reducing the number of exclamation marks.

Reducing the use of exclamation marks in professional documentation can help maintain a more formal tone. Consider revising to a single exclamation mark or none.


Line range hint 66-66: Consider adding a comma and the article "a" for grammatical correctness.

- For subsequent tests run the following if you want to start with fresh state
+ For subsequent tests, run the following if you want to start with a fresh state

This change adds necessary punctuation and articles to make the instructions clearer and grammatically correct.

README.md Show resolved Hide resolved
@joe-bowman
Copy link
Contributor Author

This pull request has been deployed to Vercel.

Latest commit: 4de61d6
✅ Preview: https://pr-1499.app-dev.quicksilver.zone
🔍 Inspect: https://vercel.com/quicksilver/quicksilver/Cqmo86m4CuxwY6nSVtiq91NSPzr8

View Workflow Logs

Copy link

codecov bot commented Apr 25, 2024

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 63.13%. Comparing base (736ecbc) to head (4de61d6).

Additional details and impacted files

Impacted file tree graph

@@           Coverage Diff           @@
##             main    #1499   +/-   ##
=======================================
  Coverage   63.13%   63.13%           
=======================================
  Files         192      192           
  Lines       13458    13458           
=======================================
  Hits         8497     8497           
  Misses       4151     4151           
  Partials      810      810           
Flag Coverage Δ
unittests 63.13% <ø> (ø)

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

Copy link
Contributor

@minhngoc274 minhngoc274 left a comment

Choose a reason for hiding this comment

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

LGTM

@joe-bowman joe-bowman merged commit 4d087cc into main Apr 26, 2024
26 checks passed
@joe-bowman joe-bowman deleted the fix-buf0build branch April 26, 2024 07:07
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants