-
Notifications
You must be signed in to change notification settings - Fork 241
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
v1.0.2 Websocket subscriptions stop responding #812
Comments
Confirmed |
I don't reproduce the issue though:
And this feature is tested in our integration test, which also runs ok. |
I receive the first result saying is ok, but not suscriptions. Just updated my node to 1.0.2 Edit: Reset and working ok, it seems that if just updated to 1.0.2 without a restart first, it is not working...something like that must be. |
A few days later... seems i got the same issue, until i restart my node then its working again I don't get this issue when i started my node which is like 1 week before back then Submitted the issue here |
Subscriptions of all kinds across websockets are confirming subscription, but not responding with data
Code to re-produce:
wscat -c ws://127.0.0.1:8546
{"jsonrpc":"2.0","id":1,"method":"eth_subscribe","params":["newHeads"]}
Regular RPC calls are working:
The text was updated successfully, but these errors were encountered: