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: delete already refunded fees from state if some fee cannot be refunded on channel closure #6255

Merged
merged 9 commits into from
May 7, 2024

Conversation

crodriguezvega
Copy link
Contributor

@crodriguezvega crodriguezvega commented May 5, 2024

Description

While refunding fees for a packet on channel closure, some fees could be refunded and some not. Those fees that are refunded should be deleted from state, so that there is no possibility of them being refunded again if the packet fee information for a packet is used somehow.

closes: #XXXX


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
    • Updated logic in RefundFeesOnChannelClosure function to handle unrefunded fees by storing them in a new slice and updating packet fees accordingly.
  • Bug Fixes
    • Fixed a bug where refunded fees were not deleted from the state if some fees could not be refunded during channel closure.

Copy link
Contributor

coderabbitai bot commented May 5, 2024

Walkthrough

Walkthrough

The update in escrow.go involves enhancing the refund logic to address unrefunded fees by storing them in a new slice, unRefundedFees, and adjusting packet fees accordingly. This change aims to improve the handling of fee refunds upon channel closure within the app/29-fee module.

Changes

File Path Change Summary
.../29-fee/keeper/escrow.go Updated logic to manage unrefunded fees by introducing unRefundedFees.
.../29-fee/keeper/escrow_test.go Modified test declarations; removed variables locked and expectEscrowFeesToBeDeleted.
CHANGELOG.md Implemented a bug fix in the app/29-fee module to delete refunded fees from the state if some fees cannot be refunded upon channel closure.

Possibly related issues


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

Out of diff range and nitpick comments (2)
modules/apps/29-fee/keeper/escrow.go (1)

Line range hint 192-216: Refactor to improve error handling and reduce code duplication.

-			refundAddr, err := sdk.AccAddressFromBech32(packetFee.RefundAddress)
-			if err != nil {
-				unRefundedFees = append(unRefundedFees, packetFee)
-				continue
-			}
-
-			// refund all fees to refund address
-			if err = k.bankKeeper.SendCoinsFromModuleToAccount(cacheCtx, types.ModuleName, refundAddr, packetFee.Fee.Total()); err != nil {
-				unRefundedFees = append(unRefundedFees, packetFee)
-				continue
-			}
+			if err := k.attemptRefund(cacheCtx, &unRefundedFees, packetFee); err != nil {
+				return err
+			}

Consider extracting the refund logic into a separate method attemptRefund to handle the parsing of the refund address and the actual refund. This reduces duplication and improves readability.

modules/apps/29-fee/keeper/escrow_test.go (1)

Line range hint 398-563: Enhance test coverage for handling of unrefunded fees.

It appears that the tests could be enhanced to specifically verify the handling of unRefundedFees. Would you like me to help by adding detailed test cases or opening a GitHub issue to track this enhancement?

Review Details

Configuration used: .coderabbit.yml
Review profile: CHILL

Commits Files that changed from the base of the PR and between 4f02df5 and 9027b6e.
Files selected for processing (2)
  • modules/apps/29-fee/keeper/escrow.go (2 hunks)
  • modules/apps/29-fee/keeper/escrow_test.go (6 hunks)
Additional Context Used
Path-based Instructions (2)
modules/apps/29-fee/keeper/escrow.go (1)

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

modules/apps/29-fee/keeper/escrow_test.go (2)

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


Pattern **/*_test.go: "Assess the unit test code assessing sufficient code coverage for the changes associated in the pull request"

Additional comments not posted (1)
modules/apps/29-fee/keeper/escrow.go (1)

221-225: Ensure proper handling of state updates for unrefunded fees.

Please verify that the state updates using SetFeesInEscrow and DeleteFeesInEscrow are correctly implemented across the codebase, especially in scenarios where fees are partially refunded.

Copy link
Member

@damiannolan damiannolan left a comment

Choose a reason for hiding this comment

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

Thanks @crodriguezvega! Code changes look good to me.

I think in future we can:

- RefundFeesOnChannelClosure(ctx sdk.Context, portID, channelID string) error {
+ RefundFeesOnChannelClosure(ctx sdk.Context, portID, channelID string) {

It looks like the error return is not used here at all since #1523

Copy link
Member

Choose a reason for hiding this comment

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

might be nice to refactor this test in future to be a bit more clear, maybe we some expResult func or something. But happy to move ahead with this for now

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 9027b6e and cfe3b11.
Files selected for processing (1)
  • CHANGELOG.md (1 hunks)
Additional Context Used
Path-based Instructions (1)
CHANGELOG.md (1)

Pattern **/*.md: "Assess the documentation for misspellings, grammatical errors, missing documentation and correctness"

Copy link
Member

@srdtrk srdtrk left a comment

Choose a reason for hiding this comment

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

Looks good but this makes me wonder if there is a possible denial of service (for channel closure) where a user spams the chain with many packet fees over time so that the gas needed to iterate over the fees is too much.

@crodriguezvega
Copy link
Contributor Author

Looks good but this makes me wonder if there is a possible denial of service (for channel closure) where a user spams the chain with many packet fees over time so that the gas needed to iterate over the fees is too much.

Maybe we could put a limit on the number of fees that can be escrowed for a single packet?

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

Out of diff range and nitpick comments (2)
CHANGELOG.md (2)

Line range hint 170-170: Use Markdown link syntax for URLs.

- * [\#6193](https://github.com/cosmos/ibc-go/pull/6193) Bump Cosmos SDK to v0.50.6.
+ * [\#6193](https://github.com/cosmos/ibc-go/pull/6193) [Bump Cosmos SDK to v0.50.6](https://github.com/cosmos/ibc-go/pull/6193).

Line range hint 185-185: Remove trailing spaces.

- * (apps/27-interchain-accounts) [\#6167](https://github.com/cosmos/ibc-go/pull/6167) Fixed an edge case bug where migrating params for a pre-existing ica module which implemented controller functionality only could panic when migrating params for newly added host, and align controller param migration with host. 
+ * (apps/27-interchain-accounts) [\#6167](https://github.com/cosmos/ibc-go/pull/6167) Fixed an edge case bug where migrating params for a pre-existing ica module which implemented controller functionality only could panic when migrating params for newly added host, and align controller param migration with host.
Review Details

Configuration used: .coderabbit.yml
Review profile: CHILL

Commits Files that changed from the base of the PR and between cfe3b11 and dd1c478.
Files selected for processing (1)
  • CHANGELOG.md (1 hunks)
Additional Context Used
Path-based Instructions (1)
CHANGELOG.md (1)

Pattern **/*.md: "Assess the documentation for misspellings, grammatical errors, missing documentation and correctness"

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

Out of diff range and nitpick comments (2)
CHANGELOG.md (2)

Line range hint 171-171: Use descriptive text for URLs to improve readability.

- * [\#6193](https://github.com/cosmos/ibc-go/pull/6193) Bump Cosmos SDK to v0.50.6.
+ * [Bump Cosmos SDK to v0.50.6](https://github.com/cosmos/ibc-go/pull/6193).

Line range hint 186-186: Remove trailing spaces.

- * (apps/27-interchain-accounts) [\#6167](https://github.com/cosmos/ibc-go/pull/6167) Fixed an edge case bug where migrating params for a pre-existing ica module which implemented controller functionality only could panic when migrating params for newly added host, and align controller param migration with host. 
+ * (apps/27-interchain-accounts) [\#6167](https://github.com/cosmos/ibc-go/pull/6167) Fixed an edge case bug where migrating params for a pre-existing ica module which implemented controller functionality only could panic when migrating params for newly added host, and align controller param migration with host.
Review Details

Configuration used: .coderabbit.yml
Review profile: CHILL

Commits Files that changed from the base of the PR and between dd1c478 and eda884d.
Files selected for processing (1)
  • CHANGELOG.md (1 hunks)
Additional Context Used
Path-based Instructions (1)
CHANGELOG.md (1)

Pattern **/*.md: "Assess the documentation for misspellings, grammatical errors, missing documentation and correctness"

Copy link

sonarcloud bot commented May 7, 2024

Quality Gate Passed Quality Gate passed for 'ibc-go'

Issues
9 New issues
0 Accepted issues

Measures
0 Security Hotspots
No data about Coverage
No data about Duplication

See analysis details on SonarCloud

@crodriguezvega crodriguezvega merged commit 500765e into main May 7, 2024
77 of 78 checks passed
@crodriguezvega crodriguezvega deleted the carlos/delete-refunded-fees branch May 7, 2024 21:12
mergify bot pushed a commit that referenced this pull request May 7, 2024
…funded on channel closure (#6255)

* delete the refunded fees in case an error happens in the loop that refunds fees on channel closure

* test simplifications

* fix typo

* clean up code

* fix logic

* add changelog

(cherry picked from commit 500765e)

# Conflicts:
#	CHANGELOG.md
#	modules/apps/29-fee/keeper/escrow_test.go
mergify bot pushed a commit that referenced this pull request May 7, 2024
…funded on channel closure (#6255)

* delete the refunded fees in case an error happens in the loop that refunds fees on channel closure

* test simplifications

* fix typo

* clean up code

* fix logic

* add changelog

(cherry picked from commit 500765e)

# Conflicts:
#	modules/apps/29-fee/keeper/escrow_test.go
crodriguezvega added a commit that referenced this pull request May 10, 2024
…funded on channel closure (backport #6255) (#6269)

* fix: delete already refunded fees from state if some fee cannot be refunded on channel closure (#6255)

* delete the refunded fees in case an error happens in the loop that refunds fees on channel closure

* test simplifications

* fix typo

* clean up code

* fix logic

* add changelog

(cherry picked from commit 500765e)

# Conflicts:
#	CHANGELOG.md
#	modules/apps/29-fee/keeper/escrow_test.go

* fix conflicts

* add import

---------

Co-authored-by: Carlos Rodriguez <carlos@interchain.io>
crodriguezvega added a commit that referenced this pull request May 10, 2024
…funded on channel closure (backport #6255) (#6270)

* fix: delete already refunded fees from state if some fee cannot be refunded on channel closure (#6255)

* delete the refunded fees in case an error happens in the loop that refunds fees on channel closure

* test simplifications

* fix typo

* clean up code

* fix logic

* add changelog

(cherry picked from commit 500765e)

# Conflicts:
#	modules/apps/29-fee/keeper/escrow_test.go

* fix conflicts

---------

Co-authored-by: Carlos Rodriguez <carlos@interchain.io>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants