https://golang.org/cl/120558提到了这个问题：time: accept UTC offsets +13,+14 in Parse, reject -13,-14

https://golang.org/cl/130696提到了这个问题：time: allow +00 as numeric timezone name and GMT offset

+14 和 +00 现在已正确解析，降至10次失败，所有失败均由非整数UTC偏移量引起：

$ gotip run parse_timezones.go 
Timezone:    Indian/Cocos
zdump time:  Sun Aug 5 18:25:10 2018 +0630
time.Parse:  parsing time "Sun Aug 5 18:25:10 2018 +0630" as "Mon Jan 2 15:04:05 2006 MST": cannot parse "+0630" as "MST" 

Timezone:    Asia/Kabul
zdump time:  Sun Aug 5 16:25:10 2018 +0430
time.Parse:  parsing time "Sun Aug 5 16:25:10 2018 +0430" as "Mon Jan 2 15:04:05 2006 MST": cannot parse "+0430" as "MST" 

Timezone:    Australia/Lord_Howe
zdump time:  Sun Aug 5 22:25:10 2018 +1030
time.Parse:  parsing time "Sun Aug 5 22:25:10 2018 +1030" as "Mon Jan 2 15:04:05 2006 MST": cannot parse "+1030" as "MST" 

Timezone:    Australia/Eucla
zdump time:  Sun Aug 5 20:40:10 2018 +0845
time.Parse:  parsing time "Sun Aug 5 20:40:10 2018 +0845" as "Mon Jan 2 15:04:05 2006 MST": cannot parse "+0845" as "MST" 

Timezone:    Asia/Kathmandu
zdump time:  Sun Aug 5 17:40:10 2018 +0545
time.Parse:  parsing time "Sun Aug 5 17:40:10 2018 +0545" as "Mon Jan 2 15:04:05 2006 MST": cannot parse "+0545" as "MST" 

Timezone:    Pacific/Chatham
zdump time:  Mon Aug 6 00:40:10 2018 +1245
time.Parse:  parsing time "Mon Aug 6 00:40:10 2018 +1245" as "Mon Jan 2 15:04:05 2006 MST": cannot parse "+1245" as "MST" 

Timezone:    Pacific/Marquesas
zdump time:  Sun Aug 5 02:25:10 2018 -0930
time.Parse:  parsing time "Sun Aug 5 02:25:10 2018 -0930" as "Mon Jan 2 15:04:05 2006 MST": cannot parse "-0930" as "MST" 

Timezone:    Asia/Colombo
zdump time:  Sun Aug 5 17:25:10 2018 +0530
time.Parse:  parsing time "Sun Aug 5 17:25:10 2018 +0530" as "Mon Jan 2 15:04:05 2006 MST": cannot parse "+0530" as "MST" 

Timezone:    Asia/Yangon
zdump time:  Sun Aug 5 18:25:10 2018 +0630
time.Parse:  parsing time "Sun Aug 5 18:25:10 2018 +0630" as "Mon Jan 2 15:04:05 2006 MST": cannot parse "+0630" as "MST" 

Timezone:    Asia/Tehran
zdump time:  Sun Aug 5 16:25:10 2018 +0430
time.Parse:  parsing time "Sun Aug 5 16:25:10 2018 +0430" as "Mon Jan 2 15:04:05 2006 MST": cannot parse "+0430" as "MST" 

Failures:    10

我刚刚遇到了一些格式为 2019-08-22T10:41:59.006928+0000 的时间戳，我知道时间解析很复杂，但我相信上面的是符合ISO8601标准的。我相信下面的命令应该返回与 date 相同的时间，而且肯定不会出现解析失败：
| 格式 | 命令 | 结果 |
| ------------ | ------------ | ------------ |
| 2019-08-22T10:41:59.006928+0000 | date | Thu Aug 22 03:41:59 MST 2019 |
| 2019-08-22T10:41:59.006928+0000 | go | parsing time ""2019-08-22T10:41:59.006928+0000"" as ""2006-01-02T15:04:05Z07:00"": cannot parse "+0000"" as "Z07:00" |
| 2019-08-22T10:41:59.006928+00:00 | date | Thu Aug 22 03:41:59 MST 2019 |
| 2019-08-22T10:41:59.006928+00:00 | go | 2019-08-22 10:41:59.006928 +0000 +0000 |
| 2019-08-22T10:41:59.006928Z | date | Thu Aug 22 03:41:59 MST 2019 |
| 2019-08-22T10:41:59.006928Z | go | 2019-08-22 10:41:59.006928 +0000 UTC |
Go 1.8-1.12.9 的所有结果都相同。
编辑：对不起，我忘了提到它正在解析JSON。如果只是普通的字符串，我可以轻松解决这个问题。但是在没有将其 Package 在自定义类型的情况下修复JSON时间解析是没有干净的方法的，这使得处理数据结构变得不幸，因为你必须解包类型才能对其进行任何操作，或者在父类型中有多个步骤的 json.Unmarshal,这对于嵌套的出现并不容易扩展。话虽如此，我认为即使是一个简单的特殊情况，也值得在 json.Unmarshal 中修复它，即使它可以接受另一个 00 代替 :。

@cstockton 似乎可以正常工作(如果你使用正确的解析格式):

package main

import (
	"fmt"
	"time"
)

func main() {
	tstamp := "2019-08-22T10:41:59.006928+0000"
	t, err := time.Parse("2006-01-02T15:04:05-0700", tstamp)
	if err != nil {
		panic(err)
	}
	fmt.Println(t.Format(time.UnixDate))
}

https://play.golang.org/p/RjhP0xB6AtX
我错过了什么？

我正在使用JSON反序列化。

https://golang.org/cl/357450提到了这个问题：time: allow +0430,-0930 UTC offsets in Parse