Bug 501297

Summary:	Datetime - not all valid Datetime accepted -Version 2.11.80
Product:	[Applications] LabPlot2	Reporter:	Jürgen Liebmann <juergen_liebmann>
Component:	frontend	Assignee:	Alexander Semke <alexander.semke>
Status:	CONFIRMED ---
Severity:	normal
Priority:	NOR
Version First Reported In:	latest
Target Milestone:	---
Platform:	openSUSE
OS:	Linux
Latest Commit:		Version Fixed/Implemented In:
Sentry Crash Report:

Description Jürgen Liebmann 2025-03-10 11:55:10 UTC

Hi,
i have detected a strange behavior of labplot in the area of datetime:
In a spreadsheet with  a column with format datetime the input of 
2024-03-31 01:55:00 is accepted
The input of 2024-03-31 02:00:00 is r converted to 2024-03-31 03:00:00 
2024-03-31 02:00:15 in 2024-03-31 03:00:15 and so on.
This happen on all values between 2024-03-31 02:00:00 and 2024-03-31 02:59:59, 
Haven't any guess why this happens. The datetime value is  a bigint value of milliseconds since 1970 or so.

Good luck for bug hunting!


Operating System: openSUSE Tumbleweed-Slowroll 20250205
KDE Plasma Version: 6.3.2
KDE Frameworks Version: 6.11.0
Qt Version: 6.8.2
Kernel Version: 6.13.4-1.0.2.sr20250205-default (64-bit)
Graphics Platform: Wayland
Processors: 8 × Intel® Core™ i7-8550U CPU @ 1.80GHz
Memory: 14,9 GiB of RAM
Graphics Processor 1: Intel® UHD Graphics 620
Graphics Processor 2: NVIDIA GeForce 930MX
Manufacturer: HP
Product Name: HP ProBook 450 G5

Comment 1 Alexander Semke 2025-03-11 07:42:02 UTC

(In reply to Jürgen Liebmann from comment #0)
> Hi,
> i have detected a strange behavior of labplot in the area of datetime:
> In a spreadsheet with  a column with format datetime the input of 
> 2024-03-31 01:55:00 is accepted
> The input of 2024-03-31 02:00:00 is r converted to 2024-03-31 03:00:00 
> 2024-03-31 02:00:15 in 2024-03-31 03:00:15 and so on.
> This happen on all values between 2024-03-31 02:00:00 and 2024-03-31
> 02:59:59, 
> Haven't any guess why this happens. The datetime value is  a bigint value of
> milliseconds since 1970 or so.
This is because of the 1h difference for UTC... Thank you for reporting this issue, we'll fix it!