this post was submitted on 30 Jul 2023
1270 points (98.6% liked)

Lemmy.World Announcements

29161 readers
50 users here now

This Community is intended for posts about the Lemmy.world server by the admins.

Follow us for server news ๐Ÿ˜

Outages ๐Ÿ”ฅ

https://status.lemmy.world/

For support with issues at Lemmy.world, go to the Lemmy.world Support community.

Support e-mail

Any support requests are best sent to info@lemmy.world e-mail.

Report contact

Donations ๐Ÿ’—

If you would like to make a donation to support the cost of running this platform, please do so at the following donation URLs.

If you can, please use / switch to Ko-Fi, it has the lowest fees for us

Ko-Fi (Donate)

Bunq (Donate)

Open Collective backers and sponsors

Patreon

Join the team

founded 2 years ago
MODERATORS
 

Update The upgrade was done, DB migrations took around 5 minutes. We'll keep an eye out for (new) issues but for now it seems to be OK.

Original message We will upgrade lemmy.world to 0.18.3 today at 20:00 UTC+2 (Check what this isn in your timezone). Expect the site to be down for a few minutes. ""Edit"" I was warned it could be more than a few minutes. The database update might even take 30 minutes or longer.

Release notes for 0.18.3 can be found here: https://github.com/LemmyNet/lemmy/blob/main/RELEASES.md

(This is unrelated to the downtimes we experienced lately, those are caused by attacks that we're still looking into mitigating. Sorry for those)

you are viewing a single comment's thread
view the rest of the comments
[โ€“] ruud@lemmy.world 29 points 1 year ago (1 children)

Thanks, will put this in the post

[โ€“] quaddo@reddthat.com 18 points 1 year ago (2 children)

Fwiw, it can be helpful to call out the date for such changes. Preferably in YYYY-MM-DD (ISO 8601).

While it's helpful to link to an off-site timezone converter tool (thanks for that, btw), "today" can be a different date, depending on where in the world you are. For example, Japan, Australia, and New Zealand.

[โ€“] ruud@lemmy.world 15 points 1 year ago (1 children)
[โ€“] TheBananaKing@lemmy.world 11 points 1 year ago (1 children)

Even better is "when this post is N hours old" :)

[โ€“] quaddo@reddthat.com 3 points 1 year ago

As someone who has had to grind through heaps of logs over the years, from systems in various timezones, from products that disagreed on the 'best' datetime format, I've become a fan of adopting ISO 8601 as much as possible. For personal systems such as a laptop, that's a different story. But if I'm spinning up an EC2 instance in us-west-2 or a VM in Central Europe, I avoid the whole "err, what TZ is this in, or should even be in?" decision-making process and just run with WHO CARES IT'S SET TO UTC NOW LET'S MOVE ON ALREADY ๐Ÿ˜€

And not that anyone here is likely to care, but here's a quick shout out to lnav - The Logfile Navigator for grinding on system logs (for systems where something like Prometheus or whatever hasn't been proactively set up).

[โ€“] Rai@lemmy.dbzer0.com 1 points 1 year ago

ISO8601 is the only way to go.