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(baseapp): correctly set header info time on query ctx #22732

Merged
merged 2 commits into from
Dec 3, 2024

Conversation

damiannolan
Copy link
Contributor

@damiannolan damiannolan commented Dec 3, 2024

Description

The diff fixes this failing e2e test: https://github.com/cosmos/ibc-go/actions/runs/12123056947/job/33797953598?pr=7587
Verified on local run. Source of failure: https://github.com/cosmos/ibc-go/blob/main/modules/light-clients/07-tendermint/client_state.go#L97-L100

ctx.BlockTime() now returns headerInfo.Time which needs to be set for backwards compat when using UnwrapSDKContext.


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 error handling and logging for improved debugging.
    • Improved context management to prevent inconsistent behavior during proposals.
  • Bug Fixes

    • Addressed issues related to context clearing and block finalization notifications.

@damiannolan damiannolan added the backport/v0.52.x PR scheduled for inclusion in the v0.52's next stable release label Dec 3, 2024
Copy link
Contributor

coderabbitai bot commented Dec 3, 2024

📝 Walkthrough

Walkthrough

The pull request introduces several modifications to the baseapp/abci.go file, focusing on enhancing error handling, context management, and logging within the BaseApp struct. Key changes include improvements to the CreateQueryContextWithCheckHeader method for setting timestamps, resetting context data in getContextForProposal, and adding deferred error checks in FinalizeBlock. Additionally, logging enhancements provide more detailed failure information, and the workingHash method now logs state changes during the commit phase.

Changes

File Change Summary
baseapp/abci.go - Enhanced error handling in CreateQueryContextWithCheckHeader (added Time to HeaderInfo).
- Updated getContextForProposal to clear context data during proposal preparation.
- Added deferred function in FinalizeBlock for streaming service hooks.
- Improved error logging in ExtendVote and VerifyVoteExtension methods.
- Updated workingHash to log all writes for better traceability.

Possibly related PRs

Suggested reviewers

  • aaronc
  • kocubinski
  • facundomedica
  • testinginprod
  • tac0turtle
  • 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

github-actions bot commented Dec 3, 2024

@damiannolan 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: 0

🧹 Outside diff range and nitpick comments (4)
baseapp/abci.go (4)

Line range hint 1207-1207: Handle error returned by CacheContext()

At line 1207, the error returned by CacheContext() is ignored. According to the Uber Go Style Guide, errors should not be silently ignored. Ignoring errors can lead to unintended behavior or panics if the context is nil.

Apply this diff to handle the error:

 func (app *BaseApp) getContextForProposal(ctx sdk.Context, height int64) sdk.Context {
   if height == app.initialHeight {
-    ctx, _ = app.finalizeBlockState.Context().CacheContext()
+    var err error
+    ctx, err = app.finalizeBlockState.Context().CacheContext()
+    if err != nil {
+      app.logger.Error("failed to cache context", "height", height, "err", err)
+      return ctx
+    }
     // clear all context data set during InitChain to avoid inconsistent behavior
     ctx = ctx.WithHeaderInfo(coreheader.Info{}).WithBlockHeader(cmtproto.Header{})
     return ctx
   }
   return ctx
 }

Line range hint 1084-1109: Potential nil pointer dereference in deferred function

In the FinalizeBlock method, the deferred function may dereference a nil res if an error occurs before res is assigned. This can lead to a runtime panic.

Add a nil check before using *res:

 defer func() {
-  for _, streamingListener := range app.streamingManager.ABCIListeners {
-    if err := streamingListener.ListenFinalizeBlock(app.finalizeBlockState.Context(), *req, *res); err != nil {
-      app.logger.Error("ListenFinalizeBlock listening hook failed", "height", req.Height, "err", err)
+  if res != nil {
+    for _, streamingListener := range app.streamingManager.ABCIListeners {
+      if err := streamingListener.ListenFinalizeBlock(app.finalizeBlockState.Context(), *req, *res); err != nil {
+        app.logger.Error("ListenFinalizeBlock listening hook failed", "height", req.Height, "err", err)
+      }
     }
+  } else {
+    app.logger.Error("FinalizeBlock response is nil", "height", req.Height)
   }
 }()

Line range hint 809-817: Incorrect variable in panic log statement

Within the deferred function in ExtendVote, the log statement uses err instead of r to log the panic value. This results in incorrect panic information being logged.

Update the log statement to use r:

 defer func() {
   if r := recover(); r != nil {
     app.logger.Error(
       "panic recovered in ExtendVote",
       "height", req.Height,
       "hash", fmt.Sprintf("%X", req.Hash),
-      "panic", err,
+      "panic", r,
     )
     err = fmt.Errorf("recovered application panic in ExtendVote: %v", r)
   }
 }()

Line range hint 903-907: Include hash in error log for consistency

In the VerifyVoteExtension method, the error log does not include the block hash. Including the hash, as done in ExtendVote, provides better context for debugging.

Update the log statement to include the hash:

 app.logger.Error("failed to verify vote extension", 
   "height", req.Height,
+  "hash", fmt.Sprintf("%X", req.Hash),
   "err", err)
📜 Review details

Configuration used: .coderabbit.yml
Review profile: CHILL

📥 Commits

Reviewing files that changed from the base of the PR and between 5426cd8 and d1e8a44.

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

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

@damiannolan
Copy link
Contributor Author

Is this also missing from header info in ExtendVote? should it be setting time based off of process proposal appstate?

Copy link
Member

@julienrbrt julienrbrt left a comment

Choose a reason for hiding this comment

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

utACK

@julienrbrt julienrbrt changed the title fix: correctly set header info time on query ctx fix(baseapp): correctly set header info time on query ctx Dec 3, 2024
@tac0turtle tac0turtle enabled auto-merge December 3, 2024 16:41
@tac0turtle tac0turtle added this pull request to the merge queue Dec 3, 2024
@github-merge-queue github-merge-queue bot removed this pull request from the merge queue due to failed status checks Dec 3, 2024
@julienrbrt julienrbrt added this pull request to the merge queue Dec 3, 2024
Merged via the queue into main with commit 371e05a Dec 3, 2024
84 of 85 checks passed
@julienrbrt julienrbrt deleted the damian/fix-ctx-blocktime-for-grpc-queries branch December 3, 2024 21:16
mergify bot pushed a commit that referenced this pull request Dec 3, 2024
julienrbrt pushed a commit that referenced this pull request Dec 3, 2024
…22732) (#22737)

Co-authored-by: Damian Nolan <damiannolan@gmail.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
backport/v0.52.x PR scheduled for inclusion in the v0.52's next stable release
Projects
None yet
Development

Successfully merging this pull request may close these issues.

7 participants