this post was submitted on 13 Sep 2023
18 points (100.0% liked)
Beehaw Support
2796 readers
1 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.
founded 2 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
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. 😂
(not to defend lemmy more generally, but timestamps and databases are god's punishment for the hubris of software devs)
Ah, that explains why I was seeing Java datetime errors instead of the timestamps in Sync.