Comment 29 for bug 982210
Revision history for this message
|
|
#29 |
© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
bbfa235
(Get the code!)
The problem here may be that QDateTime can return -1 for invalid dates. Cast to a 32-bit unsigned int, -1 is 4294967295, and interpreted as a timestamp that's exactly 2106-02-07 07:28. The code doesn’t handle this case, as far as I can tell.
Notably, I’ve had this happen with completely valid feeds with correct time zone and ISO time strings. I’m not sure what the root cause is. The same feeds will work if I delete all Akregator settings and import it anew.