mirror of
https://github.com/JakeStanger/Rofi_MPD.git
synced 2026-07-11 11:14:38 +01:00
[GH-ISSUE #3] Bug: albums without month-day in their epoch #2
Labels
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
JakeStanger/Rofi_MPD#2
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @rubdos on GitHub (Oct 5, 2018).
Original GitHub issue: https://github.com/JakeStanger/Rofi_MPD/issues/3
Apparently I have albums with only year and month in their date... :-)
@JakeStanger commented on GitHub (Oct 5, 2018):
Can you check if #5 fixes this? If not I'll look into it later.
@rubdos commented on GitHub (Oct 5, 2018):
Not sure, I get another one now (more relevant in #4 than here):
@JakeStanger commented on GitHub (Oct 5, 2018):
Ok I'm hoping
ff40f69905andff4561efix this. I've implemented some basic date error correction that should stop the crashing at least.@rubdos commented on GitHub (Oct 8, 2018):
I still have the invalid stuff with year 0. I'll try to fix it myself and submit a MR.
@JakeStanger commented on GitHub (Oct 8, 2018):
https://github.com/JakeStanger/Rofi_MPD/pull/11#issuecomment-427903150
@JakeStanger commented on GitHub (Oct 8, 2018):
Ok I've looked into it further and done some testing; I was just missing a check for dates with years only.
Unix timestamps work (in python at least) backwards a long way so I'll keep it for now unless anything else pops up. The program works (for me at least) with any track dated from the year 1 to whatever the datetime limit is (9999 I think?).
@rubdos commented on GitHub (Oct 9, 2018):
Is that on Windows? Because these timestamps are literally OS dependent, and on Unix, I cannot imagine them going back before 1905 (negative 1<<32 - 1 seconds before 1970).
@rubdos commented on GitHub (Oct 9, 2018):
Hmm, since your last commit, the thing actually starts. So clamping 1 -- 9999 seems to work here.
@JakeStanger commented on GitHub (Oct 9, 2018):
I've only tested this on Linux. This is in Python don't forget, so the "Unix timestamp" is actually an arbitrarily long integer representing the number of seconds offset from 1970. Theoretically it should be able to go infinitely far forwards or back.
I don't know how OS dependent it is, but this works on Arch Linux for me at least.
@rubdos commented on GitHub (Oct 9, 2018):
Yeh well, it seems fixed :-)