id,node_id,number,title,user,state,locked,assignee,milestone,comments,created_at,updated_at,closed_at,author_association,active_lock_reason,draft,pull_request,body,reactions,performed_via_github_app,state_reason,repo,type 877016428,MDExOlB1bGxSZXF1ZXN0NjMxMDUwNjgw,5264,Numpy string coding,23625371,closed,0,,,18,2021-05-06T02:35:55Z,2021-12-30T23:40:28Z,2021-12-30T23:39:55Z,CONTRIBUTOR,,0,pydata/xarray/pulls/5264,"Fixes handling of numpy string types in coding - [x] Tests added - [x] Passes `pre-commit run --all-files` - [x] User visible changes (including notable bug fixes) are documented in `whats-new.rst` ","{""url"": ""https://api.github.com/repos/pydata/xarray/issues/5264/reactions"", ""total_count"": 0, ""+1"": 0, ""-1"": 0, ""laugh"": 0, ""hooray"": 0, ""confused"": 0, ""heart"": 0, ""rocket"": 0, ""eyes"": 0}",,,13221727,pull 990509161,MDExOlB1bGxSZXF1ZXN0NzI5MDkzNzM2,5776,Update combine error,23625371,closed,0,,,6,2021-09-08T01:05:38Z,2021-09-27T15:14:49Z,2021-09-27T14:43:15Z,CONTRIBUTOR,,0,pydata/xarray/pulls/5776,"The update points users in the direction of the `use_cftime` argument, which can solve issues where calendars are decoded into different time classes (see also the discussion in #5767) - [x] Tests added - [x] Passes `pre-commit run --all-files` - [x] User visible changes (including notable bug fixes) are documented in `whats-new.rst` ","{""url"": ""https://api.github.com/repos/pydata/xarray/issues/5776/reactions"", ""total_count"": 0, ""+1"": 0, ""-1"": 0, ""laugh"": 0, ""hooray"": 0, ""confused"": 0, ""heart"": 0, ""rocket"": 0, ""eyes"": 0}",,,13221727,pull 988426640,MDExOlB1bGxSZXF1ZXN0NzI3MzQwMDg5,5767,Open mfdataset with long time axis,23625371,closed,0,,,6,2021-09-05T05:18:14Z,2021-09-08T01:06:31Z,2021-09-08T01:06:31Z,CONTRIBUTOR,,1,pydata/xarray/pulls/5767,"When `open_mfdataset` is used on files which have a long time axis, sometimes one time axis is cast to `pd.Timestamp` whilst the other is cast to `cftime.datetime`. In such a case, xarray thinks the time co-ordinates are different and won't load and combine the files automatically. This PR identifies this issue. I've also put in a hack solution but there must be a better way to handle this edge case. - [x] Tests added - [ ] Passes `pre-commit run --all-files` - [x] User visible changes (including notable bug fixes) are documented in `whats-new.rst`","{""url"": ""https://api.github.com/repos/pydata/xarray/issues/5767/reactions"", ""total_count"": 0, ""+1"": 0, ""-1"": 0, ""laugh"": 0, ""hooray"": 0, ""confused"": 0, ""heart"": 0, ""rocket"": 0, ""eyes"": 0}",,,13221727,pull 834380377,MDExOlB1bGxSZXF1ZXN0NTk1MjA1ODQy,5050,BUG: Future time decoding,23625371,closed,0,,,3,2021-03-18T04:31:31Z,2021-03-18T14:04:09Z,2021-03-18T14:03:59Z,CONTRIBUTOR,,0,pydata/xarray/pulls/5050,"- [x] Tests added - [x] Passes `pre-commit run --all-files` - [x] User visible changes (including notable bug fixes) are documented in `whats-new.rst` This identifies (and hopefully soon fixes) an issue with decoding times that are way into the future. Without re-introducing a change made in #4684, the test fails (see https://github.com/pydata/xarray/pull/5050/checks?check_run_id=2136824754). With the change put back in, the test passes (see https://github.com/pydata/xarray/pull/5050/checks?check_run_id=2136892412). @spencerkclark can I ask for your help on this one please? It seems that the removal in #4684 caused this case (which wasn't tested) to break in v0.17 and it's unclear to me where the fix should be (I'm guessing pandas from the discussions in #4684...).","{""url"": ""https://api.github.com/repos/pydata/xarray/issues/5050/reactions"", ""total_count"": 0, ""+1"": 0, ""-1"": 0, ""laugh"": 0, ""hooray"": 0, ""confused"": 0, ""heart"": 0, ""rocket"": 0, ""eyes"": 0}",,,13221727,pull 719881097,MDExOlB1bGxSZXF1ZXN0NTAxOTk2NjI1,4506,Decoding year 1 time,23625371,closed,0,,,5,2020-10-13T05:38:58Z,2020-10-26T10:15:13Z,2020-10-26T09:50:18Z,CONTRIBUTOR,,0,pydata/xarray/pulls/4506," - [x] Closes #4422 - [x] Tests added - [x] Passes `isort . && black . && mypy . && flake8` - [x] User visible changes (including notable bug fixes) are documented in `whats-new.rst` - [x] Decision on whether to raise a warning or not when padding is performed","{""url"": ""https://api.github.com/repos/pydata/xarray/issues/4506/reactions"", ""total_count"": 0, ""+1"": 0, ""-1"": 0, ""laugh"": 0, ""hooray"": 0, ""confused"": 0, ""heart"": 0, ""rocket"": 0, ""eyes"": 0}",,,13221727,pull