Shane da Silva

Closing due to age, and not actively being pursued. Thanks!

It's possible an error occurred during Hubble's catch up sync. We've had multiple releases since then with improvements in this area, so if you're still seeing this issue after upgrading...

Hey all, we've officially deprecated the Replicator due to issues such as this one. We recommend you have a look at the [Shuttle package](https://github.com/farcasterxyz/hub-monorepo/tree/main/packages/shuttle) if you want to build a...

Hey all, we've officially deprecated the Replicator due to issues such as this one. We recommend you have a look at the [Shuttle package](https://github.com/farcasterxyz/hub-monorepo/tree/main/packages/shuttle) if you want to build a...

Sorry for the delay in response. Do you remember exactly how you reproduced this? I can see that there's a require cycle, but I'm not seeing the warning message. Example:...

Are you still seeing this, @manan19? Looking at our hubs (running 1.10.9 at time of writing) the memory usage on an instance with a 4 vCPU/30GB RAM node looks like...

Ah, makes sense. I'm going to close since we believe with the [recent min version we pushed out](https://github.com/farcasterxyz/allowlist-mainnet/pull/16/files) we should no longer have floods of gossip messages like we used...

There's been a lot of improvements shipped in Hubble (and multiple releases). If you're still seeing this with 1.12.2 or newer, let's open a new issue to track. Thanks for...

Calling out that [this comment](https://github.com/farcasterxyz/hub-monorepo/issues/1556#issuecomment-1998503281) might help shed some light on what is being observed here. Appreciate your patience as we work through identifying a path forward.

Closing as we recommend using the [Shuttle project](https://github.com/farcasterxyz/hub-monorepo/tree/main/packages/shuttle) instead of the old replicator (which has multiple issues).