This repository has been archived by the owner on Nov 6, 2020. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 1.7k
Parity SubscribeFilterLogs not displaying REMOVED events #7994
Labels
F2-bug 🐞
The client fails to follow expected behavior.
M6-rpcapi 📣
RPC API.
P2-asap 🌊
No need to stop dead in your tracks, however issue should be addressed as soon as possible.
Milestone
Comments
@ksedgwic can you please provide your calls and filters to be able to reproduce? |
5chdn
added
Z1-question 🙋♀️
Issue is a question. Closer should answer.
M6-rpcapi 📣
RPC API.
labels
Apr 4, 2018
Here is the code that subscribes to the events:
I just re-ran vs geth and we are still missing ~50% of the events |
Geth:
Parity:
|
Tbaut
added
F2-bug 🐞
The client fails to follow expected behavior.
P2-asap 🌊
No need to stop dead in your tracks, however issue should be addressed as soon as possible.
and removed
Z1-question 🙋♀️
Issue is a question. Closer should answer.
labels
Apr 6, 2018
This was referenced Apr 23, 2018
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Labels
F2-bug 🐞
The client fails to follow expected behavior.
M6-rpcapi 📣
RPC API.
P2-asap 🌊
No need to stop dead in your tracks, however issue should be addressed as soon as possible.
I'm running:
Which Parity version?: version Parity/v1.10.0-unstable-0a643a9-20180129/x86_64-linux-gnu/rustc1.22.1
Which operating system?: Linux; CentOS Linux release 7.4.1708 (Core)
How installed?: source
Are you fully synchronized?: yes
Which network are you connected to?: ethereum
Did you try to restart the node?: no
My app connects to the websocket api port and subscribes to future events pertaining to a specific ICO contract address using SubscribeFilterLogs. It pretty-prints the events it sees. When I run it side-by-side with geth (1.7.3-stable) parity's log is missing the REMOVE events (reorged transactions):
The text was updated successfully, but these errors were encountered: