this post was submitted on 13 Sep 2023
19 points (100.0% liked)

Beehaw Support

2796 readers
2 users here now

Support and meta community for Beehaw. Ask your questions about the community, technical issues, and other such things here.

A brief FAQ for lurkers and new users can be found here.

Our September 2024 financial update is here.

For a refresher on our philosophy, see also What is Beehaw?, The spirit of the rules, and Beehaw is a Community


This community's icon was made by Aaron Schneider, under the CC-BY-NC-SA 4.0 license.


if you can see this, it's up  

founded 2 years ago
MODERATORS
 

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?

top 15 comments
sorted by: hot top controversial new old
[–] Penguincoder 18 points 1 year ago (3 children)

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.

[–] ursakhiin 7 points 1 year ago (1 children)

Thanks for the update! No need to apologize! That dropping Lemmy proposal is sounding better. 😂

[–] Penguincoder 2 points 1 year ago (1 children)

Should be resolved at this time. Thanks for your patience.

[–] ursakhiin 3 points 1 year ago* (last edited 1 year ago)

It's working. Thanks for the update and your hard work!

Comment made from Connect.

[–] jdn3 4 points 1 year ago (1 children)

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?

[–] Penguincoder 3 points 1 year ago

ETA was ~ 18 hours ago. :P

No newer ETA at the moment; need to clean up the miss that caused first.

[–] d3Xt3r 3 points 1 year ago* (last edited 1 year ago)

Ah, that explains why I was seeing Java datetime errors instead of the timestamps in Sync.

[–] stoicandanxious 5 points 1 year ago

Tried on liftoff as well and it is not working.

[–] sickcoconut 4 points 1 year ago

Same with Voyager.

[–] Psynthesis 4 points 1 year ago

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.

[–] BurriedCondor@lemmy.ml 3 points 1 year ago

Also appears down accessing via Mlem

[–] m_talon 3 points 1 year ago

Yep, broken here on Liftoff too.

[–] ursakhiin 2 points 1 year ago

Definitely happening for me with Connect as well.

[–] LoamImprovement 2 points 1 year ago

Okay, I'm just glad it's not just me, I was thinking my shitty ass phone was finally giving up the ghost.

[–] Kajo 1 points 1 year ago

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.".