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: update ante handler to allow authz message #81

Merged
merged 1 commit into from
Nov 19, 2024
Merged

Conversation

beer-1
Copy link
Member

@beer-1 beer-1 commented Nov 18, 2024

Description

Bump OPinit to allow authz message to system lane and check fee granter when we check fee whitelist in free lane.

initia-labs/OPinit#126


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
    • Updated module dependencies and versions for improved compatibility.
    • Upgraded Go toolchain to version 1.23.0.
    • Incremented the github.com/initia-labs/OPinit module version from 0.6.0 to 0.6.1.

@beer-1 beer-1 requested a review from a team as a code owner November 18, 2024 14:16
@beer-1 beer-1 self-assigned this Nov 18, 2024
Copy link

coderabbitai bot commented Nov 18, 2024

Walkthrough

The pull request involves updates to the go.mod file, including an increment in the Go toolchain version from go1.22.7 to go1.23.0 and an increase in the version of the github.com/initia-labs/OPinit module from v0.6.0 to v0.6.1. Additionally, various dependencies have been added or updated, and the replace directives have been modified to point to custom versions of several modules, ensuring compatibility with the latest library versions.

Changes

File Change Summary
go.mod - Updated Go toolchain from go1.22.7 to go1.23.0
- Incremented github.com/initia-labs/OPinit from v0.6.0 to v0.6.1
- Modified require section with new dependencies and versions
- Adjusted replace directives for several modules and updated indirect dependencies

Possibly related PRs

  • bump deps #78: The changes in the go.mod file regarding dependency updates and version increments are directly related to the updates made in the main PR, which also involves modifications to the go.mod file for similar reasons.

Poem

🐰 In the meadow of code, we hop with delight,
With versions updated, everything feels right.
From go1.22 to go1.23,
New dependencies bloom, as bright as can be!
Hopping through modules, we dance and we play,
Celebrating changes, hip-hip-hooray! 🎉


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

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

🧹 Outside diff range and nitpick comments (1)
go.mod (1)

Line range hint 3-5: Critical: Invalid Go version configuration

There are several issues with the Go version configuration:

  1. The module's Go version (1.22.7) is lower than the toolchain version (1.23.0)
  2. Go 1.23.0 doesn't exist yet (latest stable version is 1.22.1 as of April 2024)

Apply this fix:

-go 1.22.7
-
-toolchain go1.23.0
+go 1.22.1
📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL

📥 Commits

Reviewing files that changed from the base of the PR and between 74021de and f8ab97d.

⛔ Files ignored due to path filters (1)
  • go.sum is excluded by !**/*.sum
📒 Files selected for processing (1)
  • go.mod (1 hunks)
🔇 Additional comments (2)
go.mod (2)

Line range hint 284-297: Verify the necessity of custom replacements

The replace directives point to custom forks, particularly noting a pending PR in cometbft-client. Let's verify if these custom replacements are still necessary.

✅ Verification successful

Custom replacements still necessary due to pending upstream changes

The verification shows that:

  • The PR in strangelove-ventures/cometbft-client (fix: bridge hook to check sender addr #10) is still open and unmerged since September 2024
  • The custom fork of cometbft is actively maintained (last commit: Nov 13, 2024)
  • The custom fork of cometbft-client contains necessary changes pending upstream merge

The replace directives are currently necessary to:

  • Use required dependency versions not yet available upstream
  • Work around the grpc version compatibility issue with cosmos/relayer
  • Maintain compatibility with custom changes in the cometbft fork
🏁 Scripts executed

The following scripts were executed for the analysis:

Script:

#!/bin/bash
# Description: Verify status of mentioned PR and necessity of custom forks

# Check if the PR in strangelove-ventures/cometbft-client is still open
gh api repos/strangelove-ventures/cometbft-client/pulls/10

# Check last commit dates of custom forks to ensure they're actively maintained
for repo in cometbft ibc-go/v8 cometbft-client; do
  echo "Checking $repo..."
  gh api repos/initia-labs/$repo/commits/HEAD | jq -r '.commit.author.date'
done

Length of output: 17710


38-38: Verify OPinit version compatibility

Let's verify that v0.6.1 of OPinit exists and contains the required ante handler changes.

@beer-1 beer-1 merged commit 071cab0 into main Nov 19, 2024
7 checks passed
@beer-1 beer-1 deleted the bump/opinit branch November 19, 2024 04:10
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.

1 participant