By waiting for a few seconds before listening to cabal-client events, the db can have time to sync with peers without the client being overwhelmed with the flood of past events.
Here's a gif of an empty db loading the current public cabal:
previously, loading the public cabal resulted in minutes of waiting and often required a few restarts or crashes to get through this initial sync.
By waiting for a few seconds before listening to cabal-client events, the db can have time to sync with peers without the client being overwhelmed with the flood of past events.
Here's a gif of an empty db loading the current public cabal:
previously, loading the public cabal resulted in minutes of waiting and often required a few restarts or crashes to get through this initial sync.