Skip to content

refactor: simplify getting abci block #166

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

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

Conversation

julienrbrt
Copy link
Member

Closes: #139

Copy link

@gemini-code-assist gemini-code-assist bot left a comment

Choose a reason for hiding this comment

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

Summary of Changes

Hello @julienrbrt, I'm Gemini Code Assist1! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

This pull request refactors the Block and Commit RPC endpoints by removing unnecessary block and commit re-signing logic. The intent is to simplify the process of getting ABCI blocks, streamlining the code by eliminating responsibilities that are no longer needed or are handled elsewhere, and cleaning up associated unused imports.

Highlights

  • Code Simplification: Removed redundant logic for re-signing the final ABCI header within the Block RPC function. This logic was previously responsible for creating a cmtproto.Vote and updating the block's signature if a signer was available.
  • Code Simplification: Removed redundant logic for re-signing the final ABCI commit within the Commit RPC function. Similar to the Block function, this logic handled creating a cmtproto.Vote and updating the commit's signature.
  • Dependency Cleanup: Removed the unused import for cmtproto (CometBFT Tendermint types protocol buffer definitions) from pkg/rpc/core/blocks.go as it is no longer required after the removal of the signing logic.
Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point in your pull request via creating an issue comment (i.e. comment on the pull request page) using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands.

Feature Command Description
Code Review /gemini review Performs a code review for the current pull request in its current state.
Pull Request Summary /gemini summary Provides a summary of the current pull request in its current state.
Comment @gemini-code-assist Responds in comments when explicitly tagged, both in issue comments and review comments.
Help /gemini help Displays a list of available commands.

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist is currently in preview and may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments to provide feedback.

You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.

Footnotes

  1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution.

Copy link
Contributor

coderabbitai bot commented Jun 26, 2025

Important

Review skipped

Draft detected.

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

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


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.

Copy link

@gemini-code-assist gemini-code-assist bot left a comment

Choose a reason for hiding this comment

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

Code Review

The pull request simplifies the process of obtaining ABCI blocks by removing the re-signing logic. The review focuses on ensuring the correctness of the BlockID and the implications of updating the commit's BlockID hash.

Comment on lines 144 to 145
BlockID: cmttypes.BlockID{Hash: abciBlock.Hash()},
Block: abciBlock,

Choose a reason for hiding this comment

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

medium

The BlockID field is being populated with the hash of the abciBlock, but the PartSetHeader is not being set. This could lead to issues if the block needs to be reconstructed from parts. Consider populating the PartSetHeader with appropriate values, or ensuring that it's handled correctly elsewhere in the code. Leaving it empty might cause unexpected behavior in CometBFT's light client or other components that rely on the PartSetHeader.

Suggested change
BlockID: cmttypes.BlockID{Hash: abciBlock.Hash()},
Block: abciBlock,
BlockID: cmttypes.BlockID{Hash: abciBlock.Hash(), PartSetHeader: cmttypes.PartSetHeader{Total: 1, Hash: abciBlock.DataHash}},

Comment on lines 215 to 216
// Update the commit's BlockID to match the final ABCI block hash
abciBlock.LastCommit.BlockID.Hash = abciBlock.Header.Hash()

Choose a reason for hiding this comment

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

medium

The commit's BlockID.Hash is being updated to match the final ABCI block hash. Ensure that this update is necessary and doesn't inadvertently affect the commit's validity or consistency, especially in light client scenarios or when verifying block integrity. Verify that this change aligns with the intended behavior of the system.

Suggested change
// Update the commit's BlockID to match the final ABCI block hash
abciBlock.LastCommit.BlockID.Hash = abciBlock.Header.Hash()
// Update the commit's BlockID to match the final ABCI block hash
abciBlock.LastCommit.BlockID.Hash = abciBlock.Header.Hash()

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.

Improve IBC efficiency
1 participant