issues: 723181209
This data as json
id | node_id | number | title | user | state | locked | assignee | milestone | comments | created_at | updated_at | closed_at | author_association | active_lock_reason | draft | pull_request | body | reactions | performed_via_github_app | state_reason | repo | type |
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
723181209 | MDU6SXNzdWU3MjMxODEyMDk= | 4516 | py38-upstream-dev failure: 'CFTimeIndex' object has no attribute '_id' | 10194086 | closed | 0 | 6 | 2020-10-16T12:39:01Z | 2020-10-23T01:08:50Z | 2020-10-23T01:08:50Z | MEMBER | Now that #4502 was fixed upstream we get a new issue in
The failure did not happen on the 14. Oct. (https://github.com/pydata/xarray/commit/db4f03e467d13229512f8f7924dc142db1b9486b the failures here are #4502) but it appeared on the 15. Oct. (https://github.com/pydata/xarray/commit/15537497136345ed67e9e8b089bcd4573df0b2ea) Maybe a change in pandas? I have not looked at it closely - maybe @spencerkclark sees what's going on? |
{ "url": "https://api.github.com/repos/pydata/xarray/issues/4516/reactions", "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
completed | 13221727 | issue |