-
Notifications
You must be signed in to change notification settings - Fork 1.7k
Missing entries in eth_getLogs response #6637
Comments
I get 937 entries with Parity/v1.6.0-unstable-32f64e9-20170914/x86_64-linux-gnu/rustc1.14.0 |
I'm getting some wierd responses from the latest Parity 1.7.2, previous version was working fine.. now half the event filters are returning empty or missing large numbers of entries. |
I just spent a few days getting my geth node back to a full sync and can confirm that geth is returning all logs correctly. Parity 1.7.2 appears to have an issue. I get 319 logs/events in geth, and 2 in Parity for my particular contract. Edit: Still broken in 1.7.3 |
Parity is pretty much unusable for live dapps because of this.. any chance we can bump the priority :) |
I'm running Parity/v1.8.2-beta-1b6588c-20171025/x86_64-macos/rustc1.21.0 with --tracing on --pruning archive. I get 937 for the above curl request. |
Can you try this web3 code... Geth returns 237 logs, Parity returns zero.
Which probably translates to something like
|
could be |
I added
to X (if X is your curl URL). I got 234 topics with that value. It came back pretty quickly too--about 2 seconds. |
Request the receipt for this transaction 0x3c587cbaf21529ac923880128dfff7213056a68c1ee926e83db95a26cfd870ea. It's the first transaction returned by the above CURL code. It's from block 0x3e90df. Here's the full returned receipt:
|
Thanks @tjayrush , i'm syncing with |
@slothbag You don't really need |
@tomusdrw I've synced with the See below for two contradictory JSON RPC calls. The first gets a transaction receipt that lists 4 logs from some address at some block. The second gets logs from this address at this block and returns an empty array where at least 4 logs are expected.
See my ethprovider script for all my parity options. Interestingly: Running @slothbag's original query returns 937 logs as expected. |
My config: I'm using warp and on the kovan testnet and I can confirm this bug. I cannot pull any logs from: The optimal would be to keep warp functionality and pull logs as required - when we query. However if we have to use --no-warp to get log visibility/functionality this needs to be mentioned in the strart up documentation. |
I'm running:
Parity version: 1.6.10
Operating system: Linux
And installed: from source
Starting params: --jsonrpc-interface all --jsonrpc-hosts=“all” --pruning archive --max-peers 100 --base-path /var/parity --geth --force-direct -l own_tx=trace --mode active --no-download --tx-queue-size 65536 --tx-queue-gas off --force-sealing --reseal-on-txs all --reseal-min-period 1000 --work-queue-size 1 --remove-solved --no-warp --tracing off --db-compaction ssd
We have 2 parity nodes, built and ran in the same way in archive mode. After initial sync is done, they start to miss events on the eth_getLogs requests(all the blocks prior to end of initial sync seem to be consistent). Interesting thing is that they are missing different logs. Previously we experienced the same behavior on 1.5.12.
Here is the query to receive events count from
0x60bf91ac87fee5a78c28f7b67701fbcfa79c18ec
contract on block span 4309200-4310200.On our nodes we receive 926 and 934 entries.
Etherscan API returns: 937 for the same request: https://api.etherscan.io/api?module=logs&action=getLogs&fromBlock=4309200&toBlock=4310200&address=0x60bf91ac87fee5a78c28f7b67701fbcfa79c18ec
If anyone has nodes in archive mode, I'd like to ask to run the same query and report the results.
Unfortunately this issue makes the filters feature in parity nodes absolutely unreliable for live environments.
The text was updated successfully, but these errors were encountered: