New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
time: A colon is missing when formatting a time zone with seconds #8497
Labels
Milestone
Comments
From the docs[0]: """" Numeric time zone offsets format as follows: -0700 ±hhmm -07:00 ±hh:mm Replacing the sign in the format with a Z triggers the ISO 8601 behavior of printing Z instead of an offset for the UTC zone. Thus: Z0700 Z or ±hhmm Z07:00 Z or ±hh:mm """" The program uses "-07:00:00" for the zone format. That's is invalid as it's none of the above supported formats. [0]: http://golang.org/pkg/time/#pkg-constants |
issue #4934 added support for parsing and formatting time zones with seconds, "-07:00:00" is a valid zone format. If you remove the colons from the format layout in the playground example I posted it will correctly print the time zone with seconds. |
https://golang.org/cl/126840043/ Status changed to Started. |
CL https://golang.org/cl/126840043 mentions this issue. |
This issue was closed by revision 298c623. Status changed to Fixed. |
wheatman
pushed a commit
to wheatman/go-akaros
that referenced
this issue
Jun 25, 2018
When formatting time zone offsets with seconds using the stdISO8601Colon and stdNumColon layouts, the colon was missing between the hour and minute parts. Fixes golang#8497. LGTM=r R=golang-codereviews, iant, gobot, r CC=golang-codereviews https://golang.org/cl/126840043
wheatman
pushed a commit
to wheatman/go-akaros
that referenced
this issue
Jul 9, 2018
When formatting time zone offsets with seconds using the stdISO8601Colon and stdNumColon layouts, the colon was missing between the hour and minute parts. Fixes golang#8497. LGTM=r R=golang-codereviews, iant, gobot, r CC=golang-codereviews https://golang.org/cl/126840043
This issue was closed.
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
The text was updated successfully, but these errors were encountered: