Thank goodness. Hope it’s tested and released soon.
otl@lemmy.sdf.org 5 months ago
Looks like there’s a fix incoming: github.com/LemmyNet/lemmy/issues/4288#issuecommen…
FYI, on lemm.ee I have been testing 0.19.1 patched with the #4330 changes by @phiresky for the past week and have noticed no further issues with outgoing federation, so I think this issue will be resolved with the next release
That patch has been applied (github.com/LemmyNet/lemmy/pull/4330) so now I guess we’re waiting for a release to be cut. Fingers crossed.
some_guy@lemmy.sdf.org 5 months ago
Pixel@lemmy.sdf.org 5 months ago
Any idea if it’ll “catch up” and sync all the messages over the past few days, or just start properly federating new stuff going forward?
CanadaPlus@lemmy.sdf.org 5 months ago
In the past, there’s been no catch up. Repost anything you want to be seen.
thisbenzingring@lemmy.sdf.org 5 months ago
Things caught up the last time. I even got replies to some of my comments
user224@lemmy.sdf.org 5 months ago
Yep. That’s a new feature of 0.19.x. It reworked how the federation works, and now it also checks if stuff federated successfully, if not, retry. It was done to make federation more reliable. But of course, new features, new bugs.
At least that’s as far as I know. Don’t trust me.
GenderNeutralBro@lemmy.sdf.org 5 months ago
I noticed some replies to my comments coming in like a day late. Not sure if that was on SDF’s end or the other servers’.
vext01@lemmy.sdf.org 5 months ago
Whh isn’t this affecting other instances?
thisbenzingring@lemmy.sdf.org 5 months ago
It is, rebooting a service/system/server or other tinkering by the instance admins has let at least one instance come back. But the bug comes back so it’s not a real solution. The instances that don’t show the problem might still have it but also have a solution watching to reset when needed.
CanadaPlus@lemmy.sdf.org 5 months ago
Until it breaks the next time. Really, they should just be less aggressive with the version they upgrade to.