Starting this morning Jerboa crashes and Connect for Lemmy shows a spinner when trying to access Beehaw. My accounts on other Lemmy instances are working fine.
Is anyone else having similar issues?
You must log in or # to comment.
Hey all. Really sorry this is happening to you. This was due to an upstream breaking change for the
latest. Essentially, the DB had stored dates as a ‘naive’ timestamp, without any timezone offset or data. The referenced Lemmy change attempts to change that to be timezone aware in all the code and PSQL. This definitely broke a lot of things. Working on implementing a fix, even if it means rolling back that update for Beehaw.Thanks for the update! No need to apologize! That dropping Lemmy proposal is sounding better. 😂
Should be resolved at this time. Thanks for your patience.
It’s working. Thanks for the update and your hard work!
Comment made from Connect.
Thanks for your response. It looks like it’s still broken on the apps, is there an estimated time for when this will be resolved?
ETA was ~ 18 hours ago. :P
No newer ETA at the moment; need to clean up the miss that caused first.
Ah, that explains why I was seeing Java datetime errors instead of the timestamps in Sync.
Tried on liftoff as well and it is not working.
Had the problem earlier with Sync. Beehaw was down last night a bit, I assume for maintenance. Sync ran an update today and I can now access in app.
deleted by creator
Same with Voyager.
Also appears down accessing via Mlem
Yep, broken here on Liftoff too.
Okay, I’m just glad it’s not just me, I was thinking my shitty ass phone was finally giving up the ghost.
Definitely happening for me with Connect as well.
deleted by creator
Same bug here with Connect (I didn’t try Jerboa). After a while, I get the error “An error occured when retrieving from beehaw.org. Details: type ‘Null’ is not a subtype of type ‘bool’ in type cast.”.
