issue_comments: 1099643203
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/6456#issuecomment-1099643203 | https://api.github.com/repos/pydata/xarray/issues/6456 | 1099643203 | IC_kwDOAMm_X85BizlD | 5635139 | 2022-04-14T21:31:37Z | 2022-04-14T21:31:37Z | MEMBER |
Right, you changed the example after I responded
Something surprising is indeed going on here. To focus on the surprising part; ```python print(ds3.low_dim.values) ds3.to_zarr('zarr_bug.zarr', mode='w') print(ds3.low_dim.values) ``` returns:
Similarly: ```python In [50]: ds3.low_dim.count().compute() Out[50]: <xarray.DataArray 'low_dim' ()> array(1000000) In [51]: ds3.to_zarr('zarr_bug.zarr', mode='w') Out[51]: <xarray.backends.zarr.ZarrStore at 0x16a27c6d0> In [55]: ds3.low_dim.count().compute() Out[55]: <xarray.DataArray 'low_dim' ()> array(500000) ``` So it's changing the result in memory just from writing to the Zarr store. I'm not sure what the cause is. We can still massively reduce the size of this example — it's currently doing pickling, got a bunch of repeated code, etc. Does it work without the pickling? What if |
{
"total_count": 0,
"+1": 0,
"-1": 0,
"laugh": 0,
"hooray": 0,
"confused": 0,
"heart": 0,
"rocket": 0,
"eyes": 0
} |
1197117301 |