Content
@
0 reply
0 recast
0 reaction
Sanjay
@sanjay
We've released 1.11.1. @wazzymandias.eth made it so that hubs will now automatically use snapshot sync to catch up if they are too many messages behind. Note that this will reset the db, if you're running a replicator you can disable this to be safe, by setting `CATCHUP_SYNC_WITH_SNAPSHOT=false` in your .env file
6 replies
2 recasts
13 reactions
jj 🛟
@jj
Hi folks, the snapshot is really awesome and fast but for me it downloaded the snapshot and then restarts the downloading of snapshots again. Looking closely at the logs I see an error message but it’s all \n so thinking there’s a typo or bug
2 replies
0 recast
0 reaction
Wasif Iqbal
@wazzymandias.eth
What do you mean "restarts the downloading of snapshots again" ? The logs in your screenshot are red herring - that's just how docker-compose renders progress bar. It's not indicative of actual error. Looks like you're progressing on snapshot download, but if you terminate before finish you'll end up re-downloading
3 replies
0 recast
0 reaction
jj 🛟
@jj
I was thinking maybe I’m missing some real errors or warnings but it says \n instead
1 reply
0 recast
0 reaction
Wasif Iqbal
@wazzymandias.eth
that's how docker-compose renders progress bar, it's not error per-se, just bad parsing
1 reply
0 recast
0 reaction
jj 🛟
@jj
Thank you for answering all these questions 🙏 just wanted sanity checks Really trying to grok hubs here to run in production You all are building basically the Linux of web3 💜
1 reply
0 recast
2 reactions
