e7db7a68f6
The date-time parser, unless it hits a fixed-width numeric field that's unfilled, leaves checking the date against its configured range until it's parsed all fields. This means it can be out of range due to a full-width field when it hits an unfilled one and tries to take the range into account when deciding whether to zero-pad or expect more input into the field. So asserting the current partially-parsed datetime is in range at that point is not justified. Thanks to Albert Astals Cid for reporting this fiendish corner case, found by oss-fuzzing of KDE's image plugins, in IRC. Pick-to: 6.7 6.5 6.2 5.15 Change-Id: Id7db7409a0b5afadafb6920a0785a4cec4c80b62 Reviewed-by: Thiago Macieira <thiago.macieira@intel.com> Reviewed-by: Albert Astals Cid <aacid@kde.org> (cherry picked from commit e0a4de17ddb924d9bf222fb3ea2d0526813edea6) Reviewed-by: Qt Cherry-pick Bot <cherrypick_bot@qt-project.org>