pull_requests: 220909991
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 |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 220909991 | MDExOlB1bGxSZXF1ZXN0MjIwOTA5OTkx | 2470 | closed | 0 | fill_value in shift | 5635139 | - [x] Closes #https://github.com/pydata/xarray/issues/2451 - [x] Tests added - [x] Tests passed - [x] Fully documented, including `whats-new.rst` for all changes and `api.rst` for new API (remove if this change should not be visible to users, e.g., if it is an internal clean-up, or if this is part of a larger project that will be documented later) Should we be more defensive around which fill_values can be passed? Currently, if the array and float values have incompatible dtypes, we don't preemtively warn or cast, apart from the case of `np.nan`, which then uses the default filler | 2018-10-06T20:33:29Z | 2018-12-28T01:07:17Z | 2018-12-27T22:58:30Z | 2018-12-27T22:58:30Z | 85ded913d030dda8eb1f3ed18db76b32a9f9ca2d | 0 | fccfe4d4286947b29070306619c171b40832df03 | 2667deb74a30dc3bd88752a3ce5da590cf7ddd48 | MEMBER | 13221727 | https://github.com/pydata/xarray/pull/2470 |
Links from other tables
- 0 rows from pull_requests_id in labels_pull_requests