issue_comments: 544864012
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/2213#issuecomment-544864012 | https://api.github.com/repos/pydata/xarray/issues/2213 | 544864012 | MDEyOklzc3VlQ29tbWVudDU0NDg2NDAxMg== | 206773 | 2019-10-22T08:46:46Z | 2019-10-22T12:09:10Z | NONE |
Nope, look at the screenshot again, the dimension is zero. The very similar issue (if not same) remains and should be considered a bug:
If I now use
However, if I use
EDIT It seems that if I create the EDIT 2 Root cause may be related to Pandas indexing using strings that encode different accuracy / resolution: http://pandas-docs.github.io/pandas-docs-travis/user_guide/timeseries.html#slice-vs-exact-match. Very contra-intuitive. Output of
|
{
"total_count": 0,
"+1": 0,
"-1": 0,
"laugh": 0,
"hooray": 0,
"confused": 0,
"heart": 0,
"rocket": 0,
"eyes": 0
} |
329066551 |


