-
Notifications
You must be signed in to change notification settings - Fork 1.7k
Parity doesn't return removed
flag on filter changes
#6880
Comments
it's NOT a bug. it's caused by insidious change in the specification on |
That said, we are aiming for compatibility between clients, so it is important to implement that soonish. @debris I don't agree that it's insubstantial, since we currently don't inform about removed log events at all - it requires quite significant change in filters logic to support that. |
removed
flag on filter cangesremoved
flag on filter changes
Note, A-labels are for pull-requests and Q-labels for issues. |
(Edit: looks like not the same issue.) |
Right now we have |
@sorpaas makes sense to me |
I think #8463 fixes the re-org messages, but only for pubsub. The regular RPC filters never had anything like that implemented (not even sure if it was ever speced), have a look here: https://github.com/paritytech/parity/blob/master/rpc/src/v1/impls/eth_filter.rs#L168-L206 |
I've installed a log filter and try to get filter changes.
Standard defines, that every emited log shouls have a
removed
field, but the logs I'm getting miss this field.The text was updated successfully, but these errors were encountered: