issue_comments: 159713922
This data as json
| html_url | issue_url | id | node_id | user | created_at | updated_at | author_association | body | reactions | performed_via_github_app | issue |
|---|---|---|---|---|---|---|---|---|---|---|---|
| https://github.com/pydata/xarray/issues/665#issuecomment-159713922 | https://api.github.com/repos/pydata/xarray/issues/665 | 159713922 | MDEyOklzc3VlQ29tbWVudDE1OTcxMzkyMg== | 6200806 | 2015-11-25T19:49:00Z | 2015-11-25T20:48:16Z | CONTRIBUTOR | @shoyer Sure, just did: #667. ~~My suspicion is that it's ultimately the same underlying issue, which is simply that these bound arrays have a 2nd dimension that xray is having a hard time dealing with. Nevertheless, that it occurs in non-time coordinates as well implies that dealing with it solely through time-related methods won't solve everything.~~ I was wrong here; see comments in #667. |
{
"total_count": 0,
"+1": 0,
"-1": 0,
"laugh": 0,
"hooray": 0,
"confused": 0,
"heart": 0,
"rocket": 0,
"eyes": 0
} |
118525173 |