-
Notifications
You must be signed in to change notification settings - Fork 1.7k
Light client does not respond to eth_getTransactionReceipt request #9133
Comments
It looks like 10 seconds interval between request and socket closed |
there is no reply to this |
i've tried to set different timeouts for OkHttpClient and still having 10 seconds socket closed so i doubt it's client fault:
|
Socker is closed too BTW ;) |
I'd be happy to assist in solving this, i can try with the latest "branch topic" source code. |
@4ntoine thanks for the report. We will investigate the problem. TL;DR; parity does not respond to |
Oh, so it's intentional behaviour? #9169 |
It's not. It's a bug :) |
Thanks for reply. Waiting for the bugfix/workaround .. |
btw any older parity version where it's responding to |
I am unable to replicate. The failing |
I did some testing on Ropsten and I will investigate this a bit more : I got a reply (it needs time as many peers reply with no response). |
Yepp, As @cheme reported this issue seems to apply for transaction receipts that are not in the |
Closed by #9318 |
Before filing a new issue, please provide the following information.
Your issue description goes here below. Try to include actual vs. expected behavior and steps to reproduce the issue.
Background
The app connects to Parity which is running in Docker over http://127.0.0.1:8545:
After connection the app subscribes to smart contract events and calls smart contract method.
I can see the transactions is actually successfully mined but since the socket is closed the app does not receive response.
Actual
Socket is closed, no response received.
Expected
Socket not closed, response received:
The text was updated successfully, but these errors were encountered: