issue_comments: 1336700669
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/pull/7356#issuecomment-1336700669 | https://api.github.com/repos/pydata/xarray/issues/7356 | 1336700669 | IC_kwDOAMm_X85PrG79 | 90008 | 2022-12-05T03:36:31Z | 2022-12-05T03:36:31Z | CONTRIBUTOR | Looking into the history a little more. I seem to be proposing to revert: https://github.com/pydata/xarray/commit/60f8c3d3488d377b0b21009422c6121e1c8f1f70 I think this is important since many users have arrays that are larger than memory. For me, I found this bug when trying to access the number of bytes in a 16GB dataset that I'm trying to load on my wimpy laptop. Not fun to start swapping. I feel like others might be hitting this too. xref: https://github.com/pydata/xarray/pull/6797 https://github.com/pydata/xarray/issues/4842 |
{
"total_count": 0,
"+1": 0,
"-1": 0,
"laugh": 0,
"hooray": 0,
"confused": 0,
"heart": 0,
"rocket": 0,
"eyes": 0
} |
1475567394 |