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
I think that eventBlock should be incremented by 1 before updating the currentBlock in the Redis cache. This is a minor issue since messageDeduplicationId should stop it from actually getting processed, however it seems like it puts unnecessary strain on the cache.
The text was updated successfully, but these errors were encountered:
@c-o-l-o-r thanks for this, def a good optimization. My initial concern was there would be multiple transactions within a block - so could intro some failure states... but this shouldn't be an issue.
If no new events occur between iterations of the contract subscriber loop, it will process the same block over and over again.
BountiesAPI/contract_subscriber/index.js
Lines 15 to 21 in fa40025
I think that
eventBlock
should be incremented by 1 before updating thecurrentBlock
in the Redis cache. This is a minor issue sincemessageDeduplicationId
should stop it from actually getting processed, however it seems like it puts unnecessary strain on the cache.The text was updated successfully, but these errors were encountered: