issue_comments: 483880786
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/2902#issuecomment-483880786 | https://api.github.com/repos/pydata/xarray/issues/2902 | 483880786 | MDEyOklzc3VlQ29tbWVudDQ4Mzg4MDc4Ng== | 1217238 | 2019-04-16T23:31:06Z | 2019-04-16T23:31:06Z | MEMBER | I think this would qualify as expected behavior. It is not a feature per-se, but is basically inevitable given the error inherent in floating point computation. I'm not entirely sure it makes sense to document this in xarray -- it's really an upstream issue from dask.array. (But again, it's totally expected for dask.) |
{
"total_count": 0,
"+1": 0,
"-1": 0,
"laugh": 0,
"hooray": 0,
"confused": 0,
"heart": 0,
"rocket": 0,
"eyes": 0
} |
433916353 |