Content pfp
Content
@
0 reply
0 recast
0 reaction

Sanjay pfp
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
18 reactions

Manan pfp
Manan
@manan
That’s a great idea. - How often does a hub do the β€œam I behind?” check? - How many is too many behind?
1 reply
0 recast
0 reaction

jj πŸ›Ÿ pfp
jj πŸ›Ÿ
@jj
Folks really love the pace of the team - it just wondering if you’re thinking of doing like an LTS type of hub versioning
1 reply
0 recast
0 reaction

jj πŸ›Ÿ pfp
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

patxol πŸ”· anser.social pfp
patxol πŸ”· anser.social
@patxol.eth
I am now regretting the upgrade. Getting the following error
1 reply
0 recast
0 reaction

Fookinnowan πŸŽ©πŸ”΅ pfp
Fookinnowan πŸŽ©πŸ”΅
@fookinnowan
The snapshot is really life saver, was having hard time to have my hub fully synced previous but from version 1.11.1 onwards the sync is a breeze πŸ‘ 222 $DEGEN
0 reply
0 recast
2 reactions

bruce pfp
bruce
@brucexc.eth
Incredible upgrade! Syncing 80M messages only took 3 hours. Amazing!πŸ‘
0 reply
0 recast
2 reactions

Adam πŸ”΅πŸŽ©πŸΉπŸŽ­ pfp
Adam πŸ”΅πŸŽ©πŸΉπŸŽ­
@tuangg
I've update to 1.11.2 πŸ‘
0 reply
0 recast
0 reaction