You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Ah, I discovered this by comparing the result of chrono::DateTime::to_rfc3339 to Python's datetime.datetime.isoformat which claims to be 8601, but I guess it is Python that is out of compliance here by showing the second-level offsets.
This code
Prints:
Note that the RFC3339 only has
+HH:MM
,+00:00
but should be+00:00:01
.This is because the code delegates to write_local_minus_utc which explicitly ignores seconds.
This bug makes chrono out of compliance with RFC3339.
The text was updated successfully, but these errors were encountered: