You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When we stream events from an event filter, ethers-rs omits fromBlock and toBlock ... those are optional args and seems like FVM implicitly requires those args, otherwise we do not receive any events when we should. They should both default to "latest" as per infura docs.
I wasn't able to verify the actual behavior from a quick glance through the code. Perhaps those args are defaulting to "latest", but the subsequent behavior is different.
What I expect to happen is when I install a filter, I can query that filter over time and receive any logs matching the filter from the block when the filter is installed until I stop querying the filter or it's uninstalled, etc.
Here's an example snippet of code using ethers-rs (the stream() method omits fromBlock and toBlock).
let events = self.contract.new_dkg_created_filter();letmut stream = events.stream().await?;
This code works with other RPCs, but never receives future events on Wallaby. However, when I add fromBlock = 'latest' and toBlock = 'latest' explicitly, I do receive the events I expect.
The text was updated successfully, but these errors were encountered:
Looked closer at the code, fromBlock and toBlock default to "latest" as expected, so this doesn't seem to be the root of my issue. Will update with more details once I figure it out.
When we stream events from an event filter, ethers-rs omits
fromBlock
andtoBlock
... those are optional args and seems like FVM implicitly requires those args, otherwise we do not receive any events when we should. They should both default to "latest" as per infura docs.https://docs.infura.io/infura/networks/ethereum/json-rpc-methods/filter-methods/eth_newfilter
I wasn't able to verify the actual behavior from a quick glance through the code. Perhaps those args are defaulting to "latest", but the subsequent behavior is different.
What I expect to happen is when I install a filter, I can query that filter over time and receive any logs matching the filter from the block when the filter is installed until I stop querying the filter or it's uninstalled, etc.
Here's an example snippet of code using ethers-rs (the
stream()
method omitsfromBlock
andtoBlock
).This code works with other RPCs, but never receives future events on Wallaby. However, when I add fromBlock = 'latest' and toBlock = 'latest' explicitly, I do receive the events I expect.
The text was updated successfully, but these errors were encountered: