High-precision timestamps generate erroneous output because unused characters of the seconds field are wrongly interpreted as a time zone offset. No error messages are generated and the resulting value is "reasonable" (desired value minus the number of seconds represented by the unparsed date), so this bug can easily result in unnoticeable data corruption.

Fix is to improve the parser, see related pull request.