Backend time parser does not parse years with more than 4 digits
Closed, ResolvedPublic
Actions

Assigned To

None

Authored By

	Tobi_WMDE_SW
	Mar 14 2014, 5:10 PM

Description

e.g. 12.12.12345 will give you "The format of the time could not be determined. Parsing failed."

Version: unspecified
Severity: critical
Whiteboard: u=dev c=backend p=5 s=2014-03-18

• bzimport raised the priority of this task from to Unbreak Now!.Nov 22 2014, 2:51 AM

• bzimport set Reference to bz62648.

• bzimport added a subscriber: Unknown Object (MLST).

This is specific to the DateTimeParser class that uses the DateTime object

Other values in other parsers work with larger years i.e.
1000000
June 202020
in 1,000,000 years
etc.

Change 119040 had a related patch set uploaded by Addshore:
Support 5+ digit years in DateTimeParser

Change 119040 merged by jenkins-bot:
Support 5+ digit years in DateTimeParser