pull_requests: 222737809
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 |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 222737809 | MDExOlB1bGxSZXF1ZXN0MjIyNzM3ODA5 | 2487 | closed | 0 | Zarr chunking (GH2300) | 31115101 | - [x] Band-aid for #2300 - [x] Test added to check that zarr-originating array can save - [x] Updated whats-new I don't fully understand the ins-and-outs of Zarr, but it seems that if it can be serialised with a smaller end-chunk to begin with, then saving a Dataset constructed from Zarr should not have an issue with that either. | 2018-10-14T19:35:06Z | 2018-11-02T04:59:19Z | 2018-11-02T04:59:04Z | 2018-11-02T04:59:04Z | f788084f6672e1325938ba2f6a0bd105aa412091 | 0 | 93990270674eb8bcbd45d3a4fa8b43200684c606 | 6d55f99905d664ef73cb708cfe8c52c2c651e8dc | CONTRIBUTOR | 13221727 | https://github.com/pydata/xarray/pull/2487 |
Links from other tables
- 0 rows from pull_requests_id in labels_pull_requests