Due to this bug that results in the Hot listing not updating, I’ve scheduled lemmy to automatically restart every hour on the hour.
When this occurs you may receive 502 errors briefly.
Due to this bug that results in the Hot listing not updating, I’ve scheduled lemmy to automatically restart every hour on the hour.
When this occurs you may receive 502 errors briefly.
Hmm good call out. I hadn’t thought about it, but would have assumed there was a DB table with pending outbound sync tasks. Kind of make sense for this to not be the case.
I think I’ll disable the restart cronjob when I can. Better to have a frozen “Hot” timeline than federation issues.
Damned if you do, damned if you don’t - I don’t know enough about Lemmy if the ram federation thing is true but no one on Git has disagreed with it yet
(Actually checking this issue #2142 it seems as if it is the outgoing federation activity sync fails that remain in ram for retry)
Yeah I’ve stopped the restart cronjob.