Occasional bug in date formatter

Question

Occasional bug in date formatter

Closed this issue 3 years ago · 4 comments

robertfmurdock commented 3 years ago

Seeing inconsistent roundtrips when using DATETIME_UTC_COMPLETE_FRACTION

Example: DateTime(1644075138096) becomes 2022-02-05T15:32:18.960Z (which is incorrect).

Tested with 2.4.13

Answer 1 · 2022-02-06T17:23:27.000Z

What would you expect to be the right result?

Answer 2 · 2022-02-06T17:25:20.000Z

The milliseconds position is wrong… needs a leading zero to go both ways If you create it, convert it, and convert it back you see the date time isn’t equal to the original Sent from ProtonMail for iOS

…

On Sun, Feb 6, 2022 at 12:23 PM, Carlos Ballesteros Velasco ***@***.***> wrote: What would you expect to be the right result? — Reply to this email directly, [view it on GitHub](#187 (comment)), or [unsubscribe](https://github.com/notifications/unsubscribe-auth/ABPNPUWT5VPK2JP6M6P3MA3UZ2VBTANCNFSM5NUEC5UQ). You are receiving this because you authored the thread.Message ID: ***@***.***>

Answer 3 · 2022-02-06T17:26:58.000Z

Then you would expect 2022-02-05T15:32:18.096Z?

Answer 4 · 2022-02-06T17:38:55.000Z

Yeah Sent from ProtonMail for iOS

…

On Sun, Feb 6, 2022 at 12:27 PM, Carlos Ballesteros Velasco ***@***.***> wrote: Then you would expect 2022-02-05T15:32:18.096Z? — Reply to this email directly, [view it on GitHub](#187 (comment)), or [unsubscribe](https://github.com/notifications/unsubscribe-auth/ABPNPUVQIANK5E7HMWOTGPLUZ2VOZANCNFSM5NUEC5UQ). You are receiving this because you authored the thread.Message ID: ***@***.***>