pull_requests: 151477771
This data as json
| 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 |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 151477771 | MDExOlB1bGxSZXF1ZXN0MTUxNDc3Nzcx | 1702 | closed | 0 | fix empty dataset from_dict | 1530840 | - [ ] Closes #xxxx - [x] Tests added / passed - [x] Passes ``git diff upstream/master **/*py | flake8 --diff`` - [ ] Fully documented, including `whats-new.rst` for all changes and `api.rst` for new API Not sure if you want an issue or a whats-new entry for a small fix like this. Also not sure how xarray tends to handle `np.array([])`. One option that I did not take was to provide ndims to `as_compatible_data` in some fashion and make sure the result comes back as having shape `(0,)*ndim` instead of just `(0,)`. | 2017-11-08T19:47:37Z | 2018-05-15T04:51:11Z | 2018-05-15T04:51:03Z | 2b220ea85d7b62c4c7737dc1446b37e8854c8f72 | 0 | 9f7e46fb04c31a58061f2fc9153a23f305b3f947 | fb6e13ec15e85bbeceedbcd754e063f6e5696bf7 | NONE | 13221727 | https://github.com/pydata/xarray/pull/1702 |
Links from other tables
- 1 row from pull_requests_id in labels_pull_requests