Skip to content
New issue

Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? # to your account

Faulty receipt check during receive packet validation #1336

Closed
Farhad-Shabani opened this issue Sep 12, 2024 · 0 comments · Fixed by #1337
Closed

Faulty receipt check during receive packet validation #1336

Farhad-Shabani opened this issue Sep 12, 2024 · 0 comments · Fixed by #1337
Assignees
Labels
A: bug Admin: something isn't working
Milestone

Comments

@Farhad-Shabani
Copy link
Member

Background

During the validation of a received packet, in case of unordered channels, there is a check where the handler look for the receipt packet by calling get_packet_receipt. If the receipt exist or not it will do nothing and treats as a no-op. But if the storage call result in any other failure than PacketReceiptNotFound the handler throw out error and recv_packet_validate fail.

Bug Summary

This is faulty and redundant check as it’s very probable that a host for non-existence case, be wrongly emitting another error variant, therefore get_packet_receipt call end up with failure instead of no-op. Besides, this storage call is redundant as in any case it's supposed to be no-op.

Version

<= 0.54.0

@Farhad-Shabani Farhad-Shabani added the A: bug Admin: something isn't working label Sep 12, 2024
@Farhad-Shabani Farhad-Shabani added this to the 0.55.0 milestone Sep 12, 2024
@github-project-automation github-project-automation bot moved this to 📥 To Do in ibc-rs Sep 12, 2024
@Farhad-Shabani Farhad-Shabani self-assigned this Sep 12, 2024
@github-project-automation github-project-automation bot moved this from 📥 To Do to ✅ Done in ibc-rs Sep 12, 2024
# for free to join this conversation on GitHub. Already have an account? # to comment
Labels
A: bug Admin: something isn't working
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant