id,node_id,number,state,locked,title,user,body,created_at,updated_at,closed_at,merged_at,merge_commit_sha,assignee,milestone,draft,head,base,author_association,auto_merge,repo,url,merged_by 622790971,MDExOlB1bGxSZXF1ZXN0NjIyNzkwOTcx,5216,closed,0,Enable using __setitem__ for Dataset using a list as key,44147817,"- [x] Closes #1123 - [x] Tests added - [x] Passes `pre-commit run --all-files` - [x] User visible changes (including notable bug fixes) are documented in `whats-new.rst` Hi xarray folks, long time user first time contributor here. I believe the tests for this feature should be expanded, so please consider this as a work in progress. Any feedback is greatly appreciated!",2021-04-25T15:57:48Z,2021-05-02T20:30:26Z,2021-05-02T20:29:34Z,2021-05-02T20:29:34Z,6c602945c717537f5282d5fdce45e2fe0f5869de,,,0,dea848760e2d6f0650d3508abd9fbd799779b765,26d6ded95a15b563acd7c984e1082457e8bd9561,CONTRIBUTOR,,13221727,https://github.com/pydata/xarray/pull/5216, 628676853,MDExOlB1bGxSZXF1ZXN0NjI4Njc2ODUz,5247,closed,0,Add to_pandas method for Dataset,44147817," - [x] Closes #255 - [x] Tests added - [x] Passes `pre-commit run --all-files` - [x] User visible changes (including notable bug fixes) are documented in `whats-new.rst` - [x] New functions/methods are listed in `api.rst` ",2021-05-02T21:04:53Z,2021-05-04T13:56:17Z,2021-05-04T13:56:00Z,2021-05-04T13:55:59Z,4aef8f9ff823cc1c5fa4e837acbfe2483110716b,,,0,acdc282c6376bf4aba14bf6f2028f172f6c0b9f6,1c198a191127c601d091213c4b3292a8bb3054e1,CONTRIBUTOR,,13221727,https://github.com/pydata/xarray/pull/5247, 638381352,MDExOlB1bGxSZXF1ZXN0NjM4MzgxMzUy,5288,closed,0,Raise error for invalid reference date for encoding time units,44147817,"- [x] Closes #5199 - [x] Tests added - [x] Passes `pre-commit run --all-files` - [x] User visible changes (including notable bug fixes) are documented in `whats-new.rst` Although the error raised by this commit does not include the whole units string, I believe it is actually more useful and specific since it focuses on the part (reference date) that's actually causing the problem. Also, the reference date is the only information available in `coding.times._ensure_padded_year`, so this is the simplest way of raising an error. I had a look in `tests/test_coding_times.py` and could not find a test for this related error raising (since I'd put a test for this commit around there) https://github.com/pydata/xarray/blob/234b40a37e484a795e6b12916315c80d70570b27/xarray/coding/times.py#L127-L129 Have I missed it? EDIT: I've tried to substitute the error raise on line 129 with a `pass` and all the tests passed anyway.",2021-05-10T20:25:23Z,2021-05-14T09:43:30Z,2021-05-13T18:27:13Z,2021-05-13T18:27:13Z,0a29ef896f6a79be2d36394dcb02857f69e0f170,,,0,701aeee15f06b36b3d3c968cea8002162d7a89eb,751f76ac95761e18d2bf2b5c7ac3c84bd2ee69ea,CONTRIBUTOR,,13221727,https://github.com/pydata/xarray/pull/5288, 644577031,MDExOlB1bGxSZXF1ZXN0NjQ0NTc3MDMx,5308,closed,0,Move encode expected test failures to own function,44147817,A quick fix for a missing commit of PR #5288,2021-05-14T09:17:30Z,2021-05-14T10:06:20Z,2021-05-14T10:06:13Z,2021-05-14T10:06:12Z,6dd080f21f332815b401ad3f51a39365d09fb56e,,,0,e92229cfbe3e7d7a161c2043b53ec3cacf8ee858,95b34f3e26633500e105d4c9a0ce963a7c587132,CONTRIBUTOR,,13221727,https://github.com/pydata/xarray/pull/5308, 685207149,MDExOlB1bGxSZXF1ZXN0Njg1MjA3MTQ5,5586,closed,0,Accept missing_dims in Variable.transpose and Dataset.transpose,44147817,"- [x] Closes #5550 - [x] Tests added - [x] Passes `pre-commit run --all-files` - [x] User visible changes (including notable bug fixes) are documented in `whats-new.rst` Regarding https://github.com/pydata/xarray/issues/5550#issuecomment-875040245, inside the for loop only a Variable's dimensions are selected for the transpose, so a dimension that it's missing in all DataArrays would just be ignored silently. Hence it's necessary to check at the beginning of the function. https://github.com/pydata/xarray/blob/5489effbe7d83451a75382f842c4f5f96ead069f/xarray/core/dataset.py#L4591",2021-07-07T13:39:15Z,2021-07-17T21:03:00Z,2021-07-17T21:02:59Z,2021-07-17T21:02:59Z,293613e82467e7c3e1c27d895f629c5b6bbec1e7,,,0,da3cec5ab15093ee1571178bfd3d3249e571a078,67d1955cc1d6941edd12a325090da7e4d029b84c,CONTRIBUTOR,,13221727,https://github.com/pydata/xarray/pull/5586, 690906592,MDExOlB1bGxSZXF1ZXN0NjkwOTA2NTky,5611,closed,0,Set coord name concat when `concat`ing along a DataArray,44147817,"- [x] Closes #5240 - [x] Tests added - [x] Passes `pre-commit run --all-files` Technically this creates user visible changes, but not sure whether it's worth adding it to the whatsnew. ",2021-07-15T17:20:54Z,2021-08-23T17:24:43Z,2021-08-23T17:00:39Z,2021-08-23T17:00:39Z,808b2e9eec1ec48d43cf9311dee27cd5550b8fd2,,,0,5de44bad35606dd7b5cba8b69787343d06314b24,4f1e2d37b662079e830c9672400fabc19b44a376,CONTRIBUTOR,,13221727,https://github.com/pydata/xarray/pull/5611, 705713175,MDExOlB1bGxSZXF1ZXN0NzA1NzEzMTc1,5680,open,0,ENH: Add default fill values for decode_cf,44147817,"- [x] Closes #2374 - [x] Tests added - [x] Passes `pre-commit run --all-files` - [ ] User visible changes (including notable bug fixes) are documented in `whats-new.rst` This is a work in progress, mostly so that I can ask some clarifying questions. I see that `netCDF4` is an optional dependency for `xarray`, so probably `import netCDF4` can't be used. Should `xarray` simply hard-code default fill values ? From the issue's conversation, it wasn't clear to me whether an argument should control the use of the default fill value. Since some tests fail now I guess the answer is yes. ",2021-08-06T19:54:05Z,2022-06-09T14:50:16Z,,,f46be84bd01a42419a8936df8d8e7f97d2151ab4,,,0,26f1b3224c5c7777765bf37999b700c34ff9ee04,d1e4164f3961d7bbb3eb79037e96cae14f7182f8,CONTRIBUTOR,,13221727,https://github.com/pydata/xarray/pull/5680, 715313013,MDExOlB1bGxSZXF1ZXN0NzE1MzEzMDEz,5713,closed,0,DOC: Remove suggestion to install pytest-xdist in docs,44147817,"- [x] Closes #5679 - [x] Passes `pre-commit run --all-files` ",2021-08-18T18:14:47Z,2021-08-19T22:16:24Z,2021-08-19T22:16:19Z,2021-08-19T22:16:19Z,efe7e5f5c0bc94085ab69341364e06877794fd33,,,0,4e6f65b02d1aa06b7c553d08d0ba1203b64df311,de867e613dc14ff80d7b898d85c4171121ad353d,CONTRIBUTOR,,13221727,https://github.com/pydata/xarray/pull/5713, 776039301,PR_kwDOAMm_X84uQWuF,5957,closed,0,Do not change coordinate inplace when throwing error,44147817,"- [x] Closes #5036 - [x] Tests added - [x] Passes `pre-commit run --all-files` - [ ] User visible changes (including notable bug fixes) are documented in `whats-new.rst` Not the prettiest of fixes, but this goes around the fact that mutable data types (e.g. when `self_data` is a `np.ndarray`) get updated inplace on the right-hand side of the following line, while the error is thrown during the subsequent assignment to the left-hand side. https://github.com/pydata/xarray/blob/20fddb7e3838d3cf1514476899e77a8a1749734b/xarray/core/variable.py#L2421 ",2021-11-08T23:10:22Z,2021-11-09T20:28:13Z,2021-11-09T20:28:13Z,2021-11-09T20:28:13Z,5871637873cd83c3a656ee6f4df86ea6628cf68a,,,0,b3541198d9a489aecf80e889aa1681c6210da059,20fddb7e3838d3cf1514476899e77a8a1749734b,CONTRIBUTOR,,13221727,https://github.com/pydata/xarray/pull/5957, 778054729,PR_kwDOAMm_X84uYCxJ,5972,closed,0,Respect keep_attrs when using `Dataset.set_index` (#4955),44147817,"- [x] Closes #4955 - [x] Tests added - [x] Passes `pre-commit run --all-files` - [ ] User visible changes (including notable bug fixes) are documented in `whats-new.rst` The original issue was about `DataArray.set_index`, but since this simply calls `Dataset.set_index`, I have only added a test for the latter. `DataArray.set_index` probably deserves a test too, please let me know what you think.",2021-11-10T22:22:31Z,2023-10-03T00:09:41Z,2023-10-03T00:09:41Z,,8b145c3ad2c9adcd3f5710d6d6620af15685c431,,,0,c47cb38235ff566272608650955dc8ee917f3fd7,d1e4164f3961d7bbb3eb79037e96cae14f7182f8,CONTRIBUTOR,,13221727,https://github.com/pydata/xarray/pull/5972,