-
Notifications
You must be signed in to change notification settings - Fork 24
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
Dropped UpdateAddHtlc #198
Comments
I don't see any issue there:
I'll have a look at the logs of our testnet node to see what happened for this payment. |
Ok I found the issue, it's actually because of another, previous HTLC.
We need to figure out why eclair-kmp sent a |
The "syncing" code in eclair-kmp looks good and it seems that messages are not sent out of order, but there may be a problem with the coroutine channel that we use to buffer outgoing messages and that is never flushed. It is possible that an outgoing message was enqueued just before the connection was lost, not sent, and picked up when we reconnected (after the initial transport handshake), I'll check with @romainbsl and update this issue |
Yes that's a perfectly reasonable exception. That looks similar to #175 but with sending socket instead of the receiving socket. |
I believe he fixed this in issue #185. The code now resets the output buffer during the connection establishment process. I believe we can close this issue. I haven't encountered it again in the last month. And if I do encounter it in the near future, it may be unrelated at this point since the code has moved so far forward. |
The client seems to have dropped an UpdateAddHtlc.
I was testing on an iOS device (iPhone 7):
The attached logs are taken from the client while it is in background mode. The logs indicates that the client:
Other notes:
Client logs
The text was updated successfully, but these errors were encountered: