techsupport

2926 readers

69 users here now

The Lemmy community will help you with your tech problems and questions about anything here. Do not be shy, we will try to help you.

If something works or if you find a solution to your problem let us know it will be greatly apreciated.

Rules: instance rules + stay on topic

Partnered communities:

You Should Know

Software gore

Recommendations

founded 2 years ago

MODERATORS

GatoB@lemmy.world

Date format bug? (infosec.pub)

submitted 2 weeks ago* (last edited 2 weeks ago) by InternetCitizen2@lemmy.world to c/techsupport@lemmy.world

3 comments fedilink hide all child comments

cross-posted from: https://lemmy.world/post/33569521

Does anyone know why the "render" of the data would be wrong? I changed it from the US format to the ISO 8601.

Edit: Adding some spaces in the equation helped.

you are viewing a single comment's thread
view the rest of the comments

[–] vk6flab@lemmy.radio 3 points 2 weeks ago (1 children)

Libre Office Version and OS?

[–] InternetCitizen2@lemmy.world 2 points 2 weeks ago (1 children)

I seemed to have solved my problem by adding spaces in the function as such =func(x, y, z). It is not clear to me why that matters, but I guess.

Version: 25.2.5.2 (X86_64) / LibreOffice Community
Build ID: 03d19516eb2e1dd5d4ccd751a0d6f35f35e08022
CPU threads: 8; OS: Linux 6.12; UI render: default; VCL: gtk3
Locale: en-US (en_US.UTF-8); UI: en-US
Flatpak
Calc: threaded

[–] PhilipTheBucket@quokk.au 3 points 2 weeks ago

Me: Oh, I've been bitten by something like that in code, I bet it's a subtle timezone issue where applying the current timezone to the 00:00:00-timestamped datetime encoding of the date, and then truncating it back to the date only, winds up shifting...

Me, after reading: What the FUCK, why