html_url,issue_url,id,node_id,user,created_at,updated_at,author_association,body,reactions,performed_via_github_app,issue
https://github.com/pydata/xarray/issues/4422#issuecomment-696787447,https://api.github.com/repos/pydata/xarray/issues/4422,696787447,MDEyOklzc3VlQ29tbWVudDY5Njc4NzQ0Nw==,2448579,2020-09-22T15:14:25Z,2020-09-22T15:14:25Z,MEMBER,"> shouldn't raise an error for 1-1-1 since that's valid according to the Climate and Forecasting netCDF conventions

OK good point. Thanks @dopplershift 

One solution would be to extract this bit of the units string and 0-pad as necessary before passing to pandas. We would have to be careful to keep the unmodified `units` attribute in encoding. 
","{""total_count"": 0, ""+1"": 0, ""-1"": 0, ""laugh"": 0, ""hooray"": 0, ""confused"": 0, ""heart"": 0, ""rocket"": 0, ""eyes"": 0}",,701062999
https://github.com/pydata/xarray/issues/4422#issuecomment-696324438,https://api.github.com/repos/pydata/xarray/issues/4422,696324438,MDEyOklzc3VlQ29tbWVudDY5NjMyNDQzOA==,2448579,2020-09-21T19:30:13Z,2020-09-21T19:30:13Z,MEMBER,"> This is an unusual format -- ordinarily we'd expect zero-padded year, month, and day values.

Can we raise an error here? Interpreting `1-1-1` as `2001-01-01` is really weird.","{""total_count"": 0, ""+1"": 0, ""-1"": 0, ""laugh"": 0, ""hooray"": 0, ""confused"": 0, ""heart"": 0, ""rocket"": 0, ""eyes"": 0}",,701062999