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(baseapp): integrate the appdata.Listener in baseapp #21965

Draft
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

cool-develope
Copy link
Contributor

@cool-develope cool-develope commented Sep 28, 2024

Description

Closes: #21526


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 (see PR Targeting)
  • provided a link to the relevant issue or specification
  • reviewed "Files changed" and left comments if necessary
  • included the necessary unit and integration tests
  • added a changelog entry to CHANGELOG.md
  • 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.

Please see Pull Request Reviewer section in the contributing guide for more information on how to review a pull request.

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

  • New Features

    • Enhanced handling of block finalization events with improved transaction and event processing.
    • Introduced new data structures for transactions and events to provide a more structured approach.
  • Bug Fixes

    • Addressed issues related to transaction handling by iterating through requests more effectively.

Copy link
Contributor

coderabbitai bot commented Sep 28, 2024

📝 Walkthrough

Walkthrough

The changes in this pull request enhance the ListenFinalizeBlock method within the listenerWrapper struct, improving the handling of block finalization events. The method now incorporates additional fields in the StartBlockData struct and expands transaction handling to include new data structures for transactions and events. This structured approach facilitates better processing of transactions and events during block finalization.

Changes

Files Change Summary
baseapp/streaming.go Updated ListenFinalizeBlock method to include new fields in StartBlockData and expanded transaction handling logic. Introduced event handling to construct Event objects from the response's events.

Assessment against linked issues

Objective Addressed Explanation
Correctly convert data from FinalizeBlockRequest into appdata.StartBlockData and appdata.TxData (#[21526])
Convert events from FinalizeBlockResponse into appdata.EventData (#[21526])
Call the appropriate StartBlock, OnTx, and OnEvent functions on Listener (#[21526])
Extract TxIndex, MsgIndex, and EventIndex attributes for appdata.Event (#[21526]) Unclear if all indices are properly extracted.

Possibly related PRs

Suggested labels

C:schema

Suggested reviewers

  • tac0turtle
  • testinginprod
  • julienrbrt

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.

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

@cool-develope your pull request is missing a changelog!

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: 3

🧹 Outside diff range and nitpick comments (1)
baseapp/streaming.go (1)

175-176: Set appropriate BlockStage for events.

Currently, BlockStage is set to appdata.UnknownBlockStage. If you know the specific block stage during which these events occur, consider setting it to the appropriate constant to improve event classification.

📜 Review details

Configuration used: .coderabbit.yml
Review profile: CHILL

📥 Commits

Files that changed from the base of the PR and between 7fe95fc and 77e3325.

📒 Files selected for processing (1)
  • baseapp/streaming.go (1 hunks)
🧰 Additional context used
📓 Path-based instructions (1)
baseapp/streaming.go (1)

Pattern **/*.go: Review the Golang code for conformity with the Uber Golang style guide, highlighting any deviations.

Comment on lines +152 to +156
if err := p.listener.StartBlock(appdata.StartBlockData{
Height: uint64(req.Height),
HeaderBytes: nil, // TODO: need to define a header struct including enc/decoding
HeaderJSON: nil, // TODO: need to define a header json struct
}); err != nil {
Copy link
Contributor

Choose a reason for hiding this comment

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

⚠️ Potential issue

Address TODOs for HeaderBytes and HeaderJSON in StartBlockData.

The HeaderBytes and HeaderJSON fields are currently set to nil, with TODO comments indicating the need to define a header struct including encoding and decoding. Implementing these fields is important for proper handling of header information in the listener.

Would you like assistance in defining the header struct and implementing the necessary encoding/decoding functions?

Comment on lines +160 to +170
if p.listener.OnTx != nil {
for i, tx := range req.Txs {
if err := p.listener.OnTx(appdata.TxData{
TxIndex: int32(i),
Bytes: func() ([]byte, error) { return tx, nil },
JSON: nil, // TODO: need to define a tx json struct
}); err != nil {
return err
}
}
}
Copy link
Contributor

Choose a reason for hiding this comment

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

⚠️ Potential issue

Implement JSON representation for transactions in TxData.

In the OnTx listener invocation, the JSON field of TxData is set to nil, with a TODO comment indicating the need to define a JSON struct for transactions. Providing a JSON representation of transactions may be important for downstream processing or indexing.

Do you need help in defining the transaction JSON struct and implementing its encoding?

Comment on lines +171 to +190
if p.listener.OnEvent != nil {
events := make([]appdata.Event, len(res.Events))
for i, event := range res.Events {
events[i] = appdata.Event{
BlockStage: appdata.UnknownBlockStage,
Type: event.Type,
Data: nil,
Attributes: func() ([]appdata.EventAttribute, error) {
attrs := make([]appdata.EventAttribute, len(event.Attributes))
for j, attr := range event.Attributes {
attrs[j] = appdata.EventAttribute{
Key: attr.Key,
Value: attr.Value,
}
}
return attrs, nil
},
}
}
}
Copy link
Contributor

Choose a reason for hiding this comment

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

⚠️ Potential issue

Events are constructed but not processed; missing call to OnEvent method.

After constructing the events slice from res.Events, the code does not invoke any method to process these events. This may result in events not being properly handled by the listener.

You may need to call p.listener.OnEvent with the constructed events slice to ensure events are processed correctly. For example:

if err := p.listener.OnEvent(events); err != nil {
    return err
}

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.

Complete main/0.52 indexer BaseApp Integration
5 participants