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
{{ message }}
This repository was archived by the owner on Oct 16, 2025. It is now read-only.
PollingBlockTracker.checkForLatestBlock() and getLatestBlock() now clear the cached block after blockReset duration when called and the PollingBlockTracker is not polling. (#348)
PollingBlockTracker.getLatestBlock() now accepts an optional parameter useCache (#340)
This option defaults to true, but when false, it ignores the cached block number and instead updates and returns a new block number, ensuring that the frequency of requests is limited to the pollingInterval period
Although we continue to maintain this, we have not used it internally for quite some time. In general we have found a polling-based approval to be reliable than a subscription-based approach. We recommend using PollingBlockTracker instead.
Fixed
Fix PollingBlockTracker.getLatestBlock so that it throws an error encountered while making the request instead of hanging, regardless of whether the request occurs inside or outside of a polling loop (#313)
Fix PollingBlockTracker.getLatestBlock so that if invoked while a previous invocation is pending, it will throw if that invocation also throws (#313)
Avoid risk of infinite retry loops when fetching new blocks (#284)
When the provider returns an error and PollingBlockTracker or SubscribeBlockTracker is destroyed, the promise returned by the getLatestBlock method will be rejected.