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

refactor: bundle the transition to FLUSHCOMPLETE into a single function #6327

Open
wants to merge 7 commits into
base: main
Choose a base branch
from

Conversation

TropicalDog17
Copy link
Contributor

@TropicalDog17 TropicalDog17 commented May 17, 2024

Description

closes: #5733


Before we can merge this PR, please make sure that all the following items have been
checked off. If any of the checklist items are not applicable, please leave them but
write a little note why.

  • Targeted PR against the correct branch (see CONTRIBUTING.md).
  • Linked to GitHub issue with discussion and accepted design, OR link to spec that describes this work.
  • Code follows the module structure standards and Go style guide.
  • Wrote unit and integration tests.
  • Updated relevant documentation (docs/).
  • Added relevant godoc comments.
  • Provide a conventional commit message to follow the repository standards.
  • Include a descriptive changelog entry when appropriate. This may be left to the discretion of the PR reviewers. (e.g. chores should be omitted from changelog)
  • Re-reviewed Files changed in the GitHub PR explorer.
  • Review SonarCloud Report in the comment section below once CI passes.

Summary by CodeRabbit

  • Refactor
    • Improved the handling of packet flushing and channel state during upgrades for better efficiency and reliability.

Copy link
Contributor

coderabbitai bot commented May 17, 2024

Walkthrough

The recent changes in the modules/core/04-channel/keeper package refactor the handling of packet flushing and channel state during upgrades. The AcknowledgePacket and TimeoutExecuted methods now delegate the handling of flush state to a new method handleFlushState. This encapsulates the logic for checking upgrade timeouts, aborting upgrades, and updating channel states, enhancing maintainability and ensuring the correct transition to FLUSHCOMPLETE.

Changes

File Path Change Summary
modules/core/04-channel/keeper/packet.go Refactored AcknowledgePacket to use handleFlushState method for flush state handling.
modules/core/04-channel/keeper/timeout.go Updated TimeoutExecuted to call handleFlushState for managing upgrade state.

Assessment against linked issues

Objective Addressed Explanation
Bundle the transition to FLUSHCOMPLETE into a single function (#5733)
Ensure two invariants: counterparty timeout has not elapsed, no in-flight packets
Refactor Ack and Confirm handlers to check timeout and perform state transition

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>.
    • 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 generate interesting stats about this repository and render them as a table.
    • @coderabbitai show all the console.log statements in this repository.
    • @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.

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 as PR comments)

  • @coderabbitai pause to pause the reviews on a PR.
  • @coderabbitai resume to resume the paused reviews.
  • @coderabbitai review to trigger a review. This is useful when automatic reviews are disabled for the repository.
  • @coderabbitai resolve resolve all the CodeRabbit review comments.
  • @coderabbitai help to get help.

Additionally, you can add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.

CodeRabbit Configration 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: 2

Review Details

Configuration used: .coderabbit.yml
Review profile: CHILL

Commits Files that changed from the base of the PR and between 76eb0da and d1aab58.
Files selected for processing (1)
  • modules/core/04-channel/keeper/packet.go (1 hunks)
Additional Context Used
Path-based Instructions (1)
modules/core/04-channel/keeper/packet.go (1)

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

Comment on lines 482 to 483
if err := k.handleFlushState(ctx, packet, channel); 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.

Tip

Codebase Verification

Ensure proper error handling in handleFlushState.

  • The handleFlushState function returns nil in several scenarios without explicitly handling errors beyond the timeout expiration. Consider adding more comprehensive error handling to cover all potential failure points.
Analysis chain

Ensure proper error handling in handleFlushState.

Scripts Executed

The following scripts were executed for the analysis:


Script:

#!/bin/bash
# Description: Verify that `handleFlushState` handles all possible error scenarios correctly.

# Test: Search for error handling in `handleFlushState`. Expect: Proper error handling for all scenarios.
rg --type go $'handleFlushState' modules/core/04-channel/keeper/packet.go

Length of output: 242



Script:

#!/bin/bash
# Extract the full implementation of the `handleFlushState` function from `packet.go`.
ast-grep --lang go --pattern $'func (k *Keeper) handleFlushState($_, $_, $_) error {
  $$$
}' modules/core/04-channel/keeper/packet.go

Length of output: 2432

Comment on lines 489 to 510
func (k *Keeper) handleFlushState(ctx sdk.Context, packet types.Packet, channel types.Channel) error {
counterpartyUpgrade, found := k.GetCounterpartyUpgrade(ctx, packet.GetSourcePort(), packet.GetSourceChannel())
if !found {
return nil
}

timeout := counterpartyUpgrade.Timeout
selfHeight, selfTimestamp := clienttypes.GetSelfHeight(ctx), uint64(ctx.BlockTime().UnixNano())

if timeout.Elapsed(selfHeight, selfTimestamp) {
// packet flushing timeout has expired, abort the upgrade and return nil,
// committing an error receipt to state, restoring the channel and successfully acknowledging the packet.
k.MustAbortUpgrade(ctx, packet.GetSourcePort(), packet.GetSourceChannel(), timeout.ErrTimeoutElapsed(selfHeight, selfTimestamp))
return nil
}

// set the channel state to flush complete if all packets have been acknowledged/flushed.
if !k.HasInflightPackets(ctx, packet.GetSourcePort(), packet.GetSourceChannel()) {
channel.State = types.FLUSHCOMPLETE
k.SetChannel(ctx, packet.GetSourcePort(), packet.GetSourceChannel(), channel)
emitChannelFlushCompleteEvent(ctx, packet.GetSourcePort(), packet.GetSourceChannel(), channel)
}
Copy link
Contributor

Choose a reason for hiding this comment

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

Review the implementation of handleFlushState.

- func (k *Keeper) handleFlushState(ctx sdk.Context, packet types.Packet, channel types.Channel) error {
+ func (k *Keeper) handleFlushState(ctx sdk.Context, packet types.Packet, channel *types.Channel) error {

Consider passing channel as a pointer to avoid copying the entire struct each time the function is called, which can improve performance especially if Channel is a large struct.


Committable suggestion

‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation.

Suggested change
func (k *Keeper) handleFlushState(ctx sdk.Context, packet types.Packet, channel types.Channel) error {
counterpartyUpgrade, found := k.GetCounterpartyUpgrade(ctx, packet.GetSourcePort(), packet.GetSourceChannel())
if !found {
return nil
}
timeout := counterpartyUpgrade.Timeout
selfHeight, selfTimestamp := clienttypes.GetSelfHeight(ctx), uint64(ctx.BlockTime().UnixNano())
if timeout.Elapsed(selfHeight, selfTimestamp) {
// packet flushing timeout has expired, abort the upgrade and return nil,
// committing an error receipt to state, restoring the channel and successfully acknowledging the packet.
k.MustAbortUpgrade(ctx, packet.GetSourcePort(), packet.GetSourceChannel(), timeout.ErrTimeoutElapsed(selfHeight, selfTimestamp))
return nil
}
// set the channel state to flush complete if all packets have been acknowledged/flushed.
if !k.HasInflightPackets(ctx, packet.GetSourcePort(), packet.GetSourceChannel()) {
channel.State = types.FLUSHCOMPLETE
k.SetChannel(ctx, packet.GetSourcePort(), packet.GetSourceChannel(), channel)
emitChannelFlushCompleteEvent(ctx, packet.GetSourcePort(), packet.GetSourceChannel(), channel)
}
func (k *Keeper) handleFlushState(ctx sdk.Context, packet types.Packet, channel *types.Channel) error {
counterpartyUpgrade, found := k.GetCounterpartyUpgrade(ctx, packet.GetSourcePort(), packet.GetSourceChannel())
if !found {
return nil
}
timeout := counterpartyUpgrade.Timeout
selfHeight, selfTimestamp := clienttypes.GetSelfHeight(ctx), uint64(ctx.BlockTime().UnixNano())
if timeout.Elapsed(selfHeight, selfTimestamp) {
// packet flushing timeout has expired, abort the upgrade and return nil,
// committing an error receipt to state, restoring the channel and successfully acknowledging the packet.
k.MustAbortUpgrade(ctx, packet.GetSourcePort(), packet.GetSourceChannel(), timeout.ErrTimeoutElapsed(selfHeight, selfTimestamp))
return nil
}
// set the channel state to flush complete if all packets have been acknowledged/flushed.
if !k.HasInflightPackets(ctx, packet.GetSourcePort(), packet.GetSourceChannel()) {
channel.State = types.FLUSHCOMPLETE
k.SetChannel(ctx, packet.GetSourcePort(), packet.GetSourceChannel(), channel)
emitChannelFlushCompleteEvent(ctx, packet.GetSourcePort(), packet.GetSourceChannel(), channel)
}

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

Review Details

Configuration used: .coderabbit.yml
Review profile: CHILL

Commits Files that changed from the base of the PR and between d1aab58 and 234c7cc.
Files selected for processing (1)
  • modules/core/04-channel/keeper/packet.go (1 hunks)
Files skipped from review as they are similar to previous changes (1)
  • modules/core/04-channel/keeper/packet.go

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

Review Details

Configuration used: .coderabbit.yml
Review profile: CHILL

Commits Files that changed from the base of the PR and between 234c7cc and fc251a6.
Files selected for processing (1)
  • modules/core/04-channel/keeper/packet.go (1 hunks)
Files skipped from review as they are similar to previous changes (1)
  • modules/core/04-channel/keeper/packet.go

Copy link
Contributor

@crodriguezvega crodriguezvega left a comment

Choose a reason for hiding this comment

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

Thanks for opening the PR, @TropicalDog17.

I would be nice if we could also replace this code with a call to handleFlushState. I just noticed actually that there might be a small bug in that code, since we are not returning if the upgrade is aborted, as the comment indicates that we should.

However, in order to replace that code you need to make sure that we exit the function only if the upgrade is aborted, since there is more logic to execute in case the upgrade is not aborted.

return nil
}

func (k *Keeper) handleFlushState(ctx sdk.Context, packet *types.Packet, channel *types.Channel) error {
Copy link
Contributor

Choose a reason for hiding this comment

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

I think it's better to return a boolean in the call site then you can do:

if aborted := k.handleFlushState(ctx, &packet, &channel); aborted == true {
  return nil
}
Suggested change
func (k *Keeper) handleFlushState(ctx sdk.Context, packet *types.Packet, channel *types.Channel) error {
func (k *Keeper) handleFlushState(ctx sdk.Context, packet *types.Packet, channel *types.Channel) bool {

selfHeight, selfTimestamp := clienttypes.GetSelfHeight(ctx), uint64(ctx.BlockTime().UnixNano())

if timeout.Elapsed(selfHeight, selfTimestamp) {
// packet flushing timeout has expired, abort the upgrade and return nil,
Copy link
Contributor

Choose a reason for hiding this comment

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

Suggested change
// packet flushing timeout has expired, abort the upgrade and return nil,
// packet flushing timeout has expired, abort the upgrade,

@TropicalDog17
Copy link
Contributor Author

@crodriguezvega thanks for your review, I've refactored accordingly.

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

Review Details

Configuration used: .coderabbit.yml
Review profile: CHILL

Commits Files that changed from the base of the PR and between fc251a6 and 0d3cfb9.
Files selected for processing (2)
  • modules/core/04-channel/keeper/packet.go (1 hunks)
  • modules/core/04-channel/keeper/timeout.go (1 hunks)
Files skipped from review as they are similar to previous changes (1)
  • modules/core/04-channel/keeper/packet.go
Additional Context Used
Path-based Instructions (1)
modules/core/04-channel/keeper/timeout.go (1)

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

Additional comments not posted (1)
modules/core/04-channel/keeper/timeout.go (1)

155-162: Refactor to centralize the transition to FLUSHCOMPLETE state.

The addition of handleFlushState within TimeoutExecuted effectively centralizes the handling of the FLUSHCOMPLETE state transition. This change aligns with the PR's objective to make the code more maintainable and less error-prone by consolidating related logic into a single function. Ensure that handleFlushState is thoroughly tested to confirm that it behaves as expected under all conditions.

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.

Bundle the transition to FLUSHCOMPLETE into a single function
3 participants