-
Notifications
You must be signed in to change notification settings - Fork 78
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
Problems to be fixed after manual tests on test-/stagenet #137
Comments
I will start with working on
|
Closed
bors bot
added a commit
that referenced
this issue
Jan 21, 2021
149: Fix Alice redeem scenario r=da-kami a=da-kami Follow up of #144, partial fix of #137 Fix Alice redeem scenario - Properly check the timelocks before trying to redeem - Distinguish different failure scenarios and reactions to it. - if we fail to construct the redeem transaction: wait for cancel. - if we fail to publish the redeem transaction: wait for cancel but let the user know that restarting the application will result in retrying to publish the tx. - if we succeed to publish the tx but then fail when waiting for finality, print error to the user (secreat already leaked, the user has to check manually if the tx was included) Co-authored-by: Daniel Karzel <daniel@comit.network>
bors bot
added a commit
that referenced
this issue
Jan 21, 2021
149: Fix Alice redeem scenario r=da-kami a=da-kami Follow up of #144, partial fix of #137 Fix Alice redeem scenario - Properly check the timelocks before trying to redeem - Distinguish different failure scenarios and reactions to it. - if we fail to construct the redeem transaction: wait for cancel. - if we fail to publish the redeem transaction: wait for cancel but let the user know that restarting the application will result in retrying to publish the tx. - if we succeed to publish the tx but then fail when waiting for finality, print error to the user (secreat already leaked, the user has to check manually if the tx was included) Co-authored-by: Daniel Karzel <daniel@comit.network>
abraham-nixon
added a commit
to abraham-nixon/xmr-btc-swap
that referenced
this issue
Feb 15, 2022
149: Fix Alice redeem scenario r=da-kami a=da-kami Follow up of #144, partial fix of comit-network/xmr-btc-swap#137 Fix Alice redeem scenario - Properly check the timelocks before trying to redeem - Distinguish different failure scenarios and reactions to it. - if we fail to construct the redeem transaction: wait for cancel. - if we fail to publish the redeem transaction: wait for cancel but let the user know that restarting the application will result in retrying to publish the tx. - if we succeed to publish the tx but then fail when waiting for finality, print error to the user (secreat already leaked, the user has to check manually if the tx was included) Co-authored-by: Daniel Karzel <daniel@comit.network>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
The following issues have to be fixed by adding
e2e
tests for edge cases:Once those two issues above are done we should add more
e2e
tests for remaining edge cases (stop application after each state and see if the application behaves as expected after resuming).Details to failure scenarios can be found in #135
Note: Scenarios involving the
cancel
path should not be actioned because for the MVP we will focus on manual recovery.The text was updated successfully, but these errors were encountered: