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

TimeoutOnClose cannot verify the closed channel proof #2534

Closed
5 tasks
yito88 opened this issue Aug 5, 2022 · 0 comments · Fixed by #2535
Closed
5 tasks

TimeoutOnClose cannot verify the closed channel proof #2534

yito88 opened this issue Aug 5, 2022 · 0 comments · Fixed by #2535
Milestone

Comments

@yito88
Copy link
Contributor

yito88 commented Aug 5, 2022

Summary of Bug

When TimeoutOnClose, the converted message has only the proof of the receipt's absence or the NextSequenceRecv. So, the process cannot verify if the counterpart channel has been closed.

Version

0.15.0

Steps to Reproduce

Try TimeoutOnClose without Mock

Acceptance Criteria

TimeoutOnClose succeeds


For Admin Use

  • Not duplicate issue
  • Appropriate labels applied
  • Appropriate milestone (priority) applied
  • Appropriate contributors tagged
  • Contributor assigned/self-assigned
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 a pull request may close this issue.

2 participants