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/3841#issuecomment-665810940,https://api.github.com/repos/pydata/xarray/issues/3841,665810940,MDEyOklzc3VlQ29tbWVudDY2NTgxMDk0MA==,14314623,2020-07-29T17:55:22Z,2020-07-29T17:55:22Z,CONTRIBUTOR,Closing in favor of [SciTools/nc-time-axis#44](https://github.com/SciTools/nc-time-axis/issues/44),"{""total_count"": 0, ""+1"": 0, ""-1"": 0, ""laugh"": 0, ""hooray"": 0, ""confused"": 0, ""heart"": 0, ""rocket"": 0, ""eyes"": 0}",,577030502
https://github.com/pydata/xarray/issues/3841#issuecomment-596023908,https://api.github.com/repos/pydata/xarray/issues/3841,596023908,MDEyOklzc3VlQ29tbWVudDU5NjAyMzkwOA==,6628425,2020-03-07T00:55:42Z,2020-03-07T00:55:42Z,MEMBER,"No worries!  Yeah, it would be great if you could post an issue there; I think you can probably come up with a more minimal example (i.e. take xarray out of it and use some synthetic data with cftime dates near year 0 as the x-coordinate).  

The fact that `cftime.DatetimeProlepticGregorian` supports years <= -1 and >= 1, but not year 0, makes things a bit awkward, but I think is based on [CF conventions](https://github.com/Unidata/cftime/issues/114#issuecomment-474840422).","{""total_count"": 0, ""+1"": 0, ""-1"": 0, ""laugh"": 0, ""hooray"": 0, ""confused"": 0, ""heart"": 0, ""rocket"": 0, ""eyes"": 0}",,577030502
https://github.com/pydata/xarray/issues/3841#issuecomment-595930317,https://api.github.com/repos/pydata/xarray/issues/3841,595930317,MDEyOklzc3VlQ29tbWVudDU5NTkzMDMxNw==,14314623,2020-03-06T19:44:10Z,2020-03-06T19:44:10Z,CONTRIBUTOR,"Apologies for not noticing this earlier. I (wrongly) assumed that xarray would handle the axis limits. Should I raise an issue over there? I am currently quite busy so it might take a while for me to be able to work on a PR.

> It looks like you can set xlim in da.plot.line - could you test this?

I tried this:
```
# This needs a good amount of dask workers!
ds = data_dict['CMIP.CSIRO.ACCESS-ESM1-5.piControl.Omon.gn']
ts.plot(xlim=['0005', '2000'])
```
and am getting the same error. ","{""total_count"": 0, ""+1"": 0, ""-1"": 0, ""laugh"": 0, ""hooray"": 0, ""confused"": 0, ""heart"": 0, ""rocket"": 0, ""eyes"": 0}",,577030502
https://github.com/pydata/xarray/issues/3841#issuecomment-595877540,https://api.github.com/repos/pydata/xarray/issues/3841,595877540,MDEyOklzc3VlQ29tbWVudDU5NTg3NzU0MA==,6628425,2020-03-06T17:32:55Z,2020-03-06T17:32:55Z,MEMBER,"I think this is probably best fixed in [nc-time-axis](https://github.com/SciTools/nc-time-axis).  It looks like it is creating generic datetimes with year 0  somewhere in [here](https://github.com/SciTools/nc-time-axis/blob/531dd0da83f2ea6b351f129559ccd4e8b0ccbb5f/nc_time_axis/__init__.py#L152-L165), which cftime does not allow for the proleptic Gregorian calendar.  The error gets thrown when trying to apply the calendar type in `utime.date2num(ticks)`.

I'm fine though with you posting this here for visibility; I'm not sure how active the nc-time-axis repo is.","{""total_count"": 0, ""+1"": 0, ""-1"": 0, ""laugh"": 0, ""hooray"": 0, ""confused"": 0, ""heart"": 0, ""rocket"": 0, ""eyes"": 0}",,577030502
https://github.com/pydata/xarray/issues/3841#issuecomment-595852733,https://api.github.com/repos/pydata/xarray/issues/3841,595852733,MDEyOklzc3VlQ29tbWVudDU5NTg1MjczMw==,10194086,2020-03-06T16:38:07Z,2020-03-06T16:38:07Z,MEMBER,It looks like you can set `xlim` in [`da.plot.line`](http://xarray.pydata.org/en/stable/generated/xarray.plot.line.html) - could you test this?,"{""total_count"": 0, ""+1"": 0, ""-1"": 0, ""laugh"": 0, ""hooray"": 0, ""confused"": 0, ""heart"": 0, ""rocket"": 0, ""eyes"": 0}",,577030502
https://github.com/pydata/xarray/issues/3841#issuecomment-595850628,https://api.github.com/repos/pydata/xarray/issues/3841,595850628,MDEyOklzc3VlQ29tbWVudDU5NTg1MDYyOA==,5635139,2020-03-06T16:33:21Z,2020-03-06T16:33:21Z,MEMBER,"Thanks for the report. 

This isn't immediately helpful to you but: any ideas why xarray isn't in the stack trace? Is this a plotting oddity?","{""total_count"": 0, ""+1"": 0, ""-1"": 0, ""laugh"": 0, ""hooray"": 0, ""confused"": 0, ""heart"": 0, ""rocket"": 0, ""eyes"": 0}",,577030502