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: check ack success if only ack is not async #2662

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

Conversation

gsk967
Copy link
Collaborator

@gsk967 gsk967 commented Jan 22, 2025

Description

closes: #XXXX


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
  • added ! to the type prefix if API or client breaking change
  • added appropriate labels to the PR
  • targeted the correct branch (see PR Targeting)
  • provided a link to the relevant issue or specification
  • added a changelog entry to CHANGELOG.md
  • included comments for documenting Go code
  • updated the relevant documentation or specification
  • reviewed "Files changed" and left comments if necessary
  • 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
  • reviewed API design and naming
  • reviewed documentation is accurate
  • reviewed tests and test coverage
  • manually tested (if applicable)

Summary by CodeRabbit

  • Tests

    • Enhanced end-to-end testing for IBC token transfers with memo
    • Added test cases to validate error handling for malformed memo deserialization
    • Improved test coverage for IBC forwarding message scenarios
  • Bug Fixes

    • Updated acknowledgment handling in IBC module to support asynchronous scenarios

@gsk967 gsk967 requested a review from a team as a code owner January 22, 2025 15:31
Copy link
Contributor

coderabbitai bot commented Jan 22, 2025

Walkthrough

This pull request introduces enhancements to IBC (Inter-Blockchain Communication) memo handling and testing across multiple files. The changes focus on improving error handling and test coverage for IBC token transfers and memo deserialization. Specifically, the modifications include adding test cases for invalid memo formats, refining acknowledgment processing in the IBC module, and expanding test scenarios for memo marshalling and deserialization.

Changes

File Change Summary
tests/e2e/e2e_ibc_memo_test.go Added test scenario for invalid IBC forwarding memo format, extending test coverage for memo handling
x/uibc/uics20/ibc_module.go Updated OnRecvPacket method to handle nil acknowledgments and improve asynchronous acknowledgment processing
x/uibc/uics20/memo_handler_test.go Added two new test cases for deserializing malformed memo JSON, enhancing error handling tests

Sequence Diagram

sequenceDiagram
    participant Client
    participant IBCModule
    participant MemoHandler
    participant Blockchain

    Client->>IBCModule: Send IBC Packet with Memo
    IBCModule->>MemoHandler: Validate Memo
    alt Invalid Memo Format
        MemoHandler-->>IBCModule: Return Error
        IBCModule-->>Client: Reject Packet
    else Valid Memo
        MemoHandler->>Blockchain: Process Memo
        Blockchain-->>IBCModule: Acknowledgment
        IBCModule-->>Client: Confirm Transaction
    end
Loading

Possibly related PRs

Poem

🐰 Hopping through blockchains with glee,
Memos dancing, errors set free!
NIL acknowledgments, no more fear,
Testing boundaries, crystal clear.
IBC rabbits, code so bright! 🌟

✨ Finishing Touches
  • 📝 Generate Docstrings (Beta)

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 generate docstrings to generate docstrings for this PR. (Beta)
  • @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
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

🧹 Nitpick comments (2)
x/uibc/uics20/ibc_module.go (1)

101-103: LGTM! Consider enhancing the documentation.

The null check for async acknowledgments is a good defensive programming practice. However, the comment could be more descriptive.

-  // ack is nil if acknowledgement is asynchronous
+  // ack can be nil for asynchronous acknowledgments, which occurs when the receiving
+  // chain needs more time to process the packet and will acknowledge it later
tests/e2e/e2e_ibc_memo_test.go (1)

89-95: Consider enhancing test coverage for acknowledgment handling.

While the test verifies balances correctly, it would be beneficial to add assertions that verify the acknowledgment behavior, especially for the async acknowledgment case that was added in ibc_module.go.

 	s.SendIBC(setup.GaiaChainID, s.Chain.ID, accs.Alice.String(), atomFromGaia, "", invalidM, "")
 	updatedIBCAtomBalance = updatedIBCAtomBalance.Add(atomFromGaia.Amount)
 	s.checkSupply(umeeAPIEndpoint, uatomIBCHash, updatedIBCAtomBalance)
 	s.checkLeverageAccountBalance(umeeAPIEndpoint, accs.Alice.String(), uatomIBCHash, atomFromGaia.Amount)
+	// Verify acknowledgment behavior
+	ack := s.GetLastAcknowledgment()
+	s.Assert().NotNil(ack, "Acknowledgment should be present for sync operations")
+	s.Assert().True(ack.Success(), "Acknowledgment should indicate success")
📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 9dfb6f1 and 87007ee.

📒 Files selected for processing (3)
  • tests/e2e/e2e_ibc_memo_test.go (1 hunks)
  • x/uibc/uics20/ibc_module.go (1 hunks)
  • x/uibc/uics20/memo_handler_test.go (1 hunks)
⏰ Context from checks skipped due to timeout of 90000ms (6)
  • GitHub Check: test-app-after-import
  • GitHub Check: test-app-import-export
  • GitHub Check: test-app-multi-seed-short
  • GitHub Check: test-e2e
  • GitHub Check: Analyze
  • GitHub Check: Summary
🔇 Additional comments (1)
x/uibc/uics20/memo_handler_test.go (1)

146-148: LGTM! Good test coverage.

The test case properly validates error handling for malformed IBC forwarding messages.

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