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
For example, Biconomy Factory initializes new instances with the initial module value. Over time, an instance will emit EnableModule and DisableModule events, changing the module list. In that scenario, it is crucial to get the factory event first and then the instance events.
When trying to setup the indexing logic like that in Ponder, we eventually run into a race condition.
Hi, thanks for opening. I was able to reproduce this on 0.2.10, but it looks like we fixed the bug that caused this in 0.2.11 yesterday. Not able to reproduce the error on 0.2.13 just now after many attempts.
Let me know if you are still seeing the issue on 0.2.13.
In some case, it might be useful.
For example, Biconomy Factory initializes new instances with the initial
module
value. Over time, an instance will emitEnableModule
andDisableModule
events, changing the module list. In that scenario, it is crucial to get the factory event first and then the instance events.When trying to setup the indexing logic like that in Ponder, we eventually run into a race condition.
To reproduce, run the indexing for the following Ponder graph: https://github.com/Destiner/ponder-biconomy (might require a few retries).
Eventually, you will run into a race condition:
Here's how the issue looks when you run into it locally:
The text was updated successfully, but these errors were encountered: