Bug 405241

Summary: MySQLe error when importing directory with far future modification / changedate
Product: [Applications] amarok Reporter: Clarence Risher <sparr0>
Component: Collections/LocalAssignee: Amarok Bugs <amarok-bugs-null>
Status: RESOLVED NOT A BUG    
Severity: normal CC: matej, ralf-engels
Priority: NOR    
Version First Reported In: 2.9.0   
Target Milestone: kf5   
Platform: Arch Linux   
OS: Linux   
Latest Commit: Version Fixed In:
Sentry Crash Report:

Description Clarence Risher 2019-03-08 20:06:21 UTC
SUMMARY

Attempting to import a directory with a modification date in the far future (threshold somewhere between 2022 and 2042) yields a mysql range error.

STEPS TO REPRODUCE
1. set folder mtime to 2042 or later
2. add folder to local collection
3. scan

OBSERVED RESULT

MySQLe query failed! (1264) Out of range value for column 'changedate' at row 1 on INSERT INTO directories(deviceid,changedate,dir) VALUES (1,3136466608,'path/to/future/directory');

EXPECTED RESULT

successful import

SOFTWARE/OS VERSIONS
Qt Version: 5.12.1
Frameworks Version: 5.55.0
Operating System: Linux 5.0.0-arch1-1-ARCH x86_64
Distribution (Platform): Archlinux Packages
Comment 1 Myriam Schweingruber 2019-03-09 02:15:59 UTC
And why would this be an Amarok error? I don't really see the point of having fake modification dates, especially in the future.
Comment 2 Bug Janitor Service 2019-03-24 04:33:11 UTC
Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least
15 days. Please provide the requested information as soon as
possible and set the bug status as REPORTED. Due to regular bug
tracker maintenance, if the bug is still in NEEDSINFO status with
no change in 30 days the bug will be closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

If you have already provided the requested information, please
mark the bug as REPORTED so that the KDE team knows that the bug is
ready to be confirmed.

Thank you for helping us make KDE software even better for everyone!
Comment 3 Bug Janitor Service 2019-04-08 04:33:14 UTC
This bug has been in NEEDSINFO status with no change for at least
30 days. The bug is now closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

Thank you for helping us make KDE software even better for everyone!