I can find it later, but I just had this issue this week with timestamps sent from a browser, supposedly in RFC3339, but Go&#x27;s RFC3339 format was not compliant with it. So naturally I made my own format template. Alas, the milliseconds part had arbitrary precision, which Go&#x27;s parser doesn&#x27;t like. So I had to revert to trying the timestamp with one, two ,three trailing digits, etc.<p>Still, this is the only issue I have with the time library, and even that has only bothered me a couple of times in 3 years of work, so no biggie. Other than that it&#x27;s indeed the best time library I&#x27;ve ever worked with.