-
Notifications
You must be signed in to change notification settings - Fork 47
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
don't receive events after some uptime #281
Comments
We're working on a new version of LoomProvider which leverages our new implementation for JSON RPC, if there's an issue, probably this issue will be sane or at least will be easier to follow. Anyway you can check our new implementation for JSON RPC today on |
We made few changes on const client = new Client('default', 'wss:https://extdev-plasma-us1.dappchains.com/websocket', 'wss:https://extdev-plasma-us1.dappchains.com/eth') Could you please check the |
Hi, I have some contracts on loom network and I wrote nodejs application for handling contract events from blockchain. Everything okay for first some hours, but some time later events didn't come. This problem is real only with uptime for some hours. When I emit event in first hour - application handle it and wrote to db, but after some hours - there are no events and I tried to debug it with debug mode and found smth interesting:
after receiving answer like
after which it sends requests for filter
and don't receive anything. maybe i messed up with logs, but i can see only this picture for latest minute or smth like that (period when transaction was sent and added to blockchain and some more time)
for all blocks i have no handled events on nodejs part (as i can see - there are no responses for filters). and this problem is coming only with time
2. are u sure that for each subscription is good idea to call node? why not better to send information about new block to client and parse it and find topics on client?
The text was updated successfully, but these errors were encountered: