-
Notifications
You must be signed in to change notification settings - Fork 1.7k
light client: subscribe over websockets doesnt send new events #8560
Comments
Could you reproduce with a full node (you can try quickly syncing on kovan)? |
Im traveling atm so Ill try to get kovan going but it might not happen, any recommendations on a chatty contract to watch? |
OK got synced and found a random contract on etherscan. New events are coming through fine on kovan full node with any filter options, so maybe the light client code? |
Thanks for narrowing down the scope. Can you edit your first post and title to reflect the fact that it's in the light client? |
I think this is worthy of inclusion on the light client dashboard? cc @tomaka |
My knowledge of events and the API around it is still limited, but I think this issue is here by design and not actually a bug. cc @rphmeier |
it should be sending new events. we should investigate if the |
I'm not sure how well this will work unless synced in general though unless we pause syncing while we check every block for log updates. |
@rphmeier Happy to test, though not sure what. Can you link or provide a snippet? |
Also would like to learn how to gdb cargo builds but havent figured that out yet if anyone has a workflow for parity that would be ideal. |
Not sure if its related to the light client or websocket. If I use a recent from block I get some events, if I use latest I get nothing, and either way I never get any new events (as I can open a second script attached to infura's websocket)
Before filing a new issue, please provide the following information.
The text was updated successfully, but these errors were encountered: