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
Receiver doesn't see EventPaymentReceivedSuccess #2461
Comments
Can you go into a bit more details about what you are doing?
|
@LefterisJP Sure: Raiden Client Log files:Sender (on Port 5009) Sender_address = The Payment was initialized by the API call:
The Response was
Payment API requestsReceivers payment history request:
Response:
Senders payment history request
Response:
|
I can verify that this is a problem. I thought we fixed it with https://github.com/raiden-network/raiden/pull/2382/files |
And it's very weird that the |
Related to #2373 that should have been fixed already |
@LefterisJP Yes, I can confirm that it's still a problem. I just now tried with latest master again and it is indeed a problem. |
Ah damn I think I see the problem. |
Fix raiden-network#2461 [ci integration]
Fix raiden-network#2461 [ci integration]
Fix raiden-network#2461 [ci integration]
Problem Definition
When sending a sucessfull Tx between two locally running nodes (I ran the nodes in debug mode and saw the EventPaymentSentSuccess in the senders and the receivers Raiden client) the receiver doesn't store the event correctly.
Meaning that querying the payment history between S and R after the Tx:
The S response will be the expected EventPaymentSentSuccess.
While the R node does return an empty list.
System Description
Ubuntu 18.04, python3.6, Raiden version 0.8.1.dev78+g9373c616 (latest master on Tuesday 13.09)
The text was updated successfully, but these errors were encountered: