pull_requests: 595205842
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 |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 595205842 | MDExOlB1bGxSZXF1ZXN0NTk1MjA1ODQy | 5050 | closed | 0 | BUG: Future time decoding | 23625371 | - [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...). | 2021-03-18T04:31:31Z | 2021-03-18T14:04:09Z | 2021-03-18T14:03:59Z | 2021-03-18T14:03:59Z | fbd48d4307502f7dbe8afa37b84df59e74407820 | 0 | 5c75f66ae670c06131a2bc3763d5bf13453b156f | a6f51c680f4e4c3ed5101b9c1111f0b94d28a781 | CONTRIBUTOR | 13221727 | https://github.com/pydata/xarray/pull/5050 |
Links from other tables
- 0 rows from pull_requests_id in labels_pull_requests