issue_comments

Table actions

2 rows where issue = 927617256 and user = 1217238 sorted by updated_at descending

✎ View and edit SQL

This data as json, CSV (advanced)

Suggested facets: created_at (date), updated_at (date)

user 1

  • shoyer · 2 ✖

issue 1

  • Appending data to a dataset stored in Zarr format produce PermissonError or NaN values in the final result · 2 ✖

author_association 1

id html_url issue_url node_id user created_at updated_at ▲ author_association body reactions performed_via_github_app issue
1546951468 https://github.com/pydata/xarray/issues/5511#issuecomment-1546951468 https://api.github.com/repos/pydata/xarray/issues/5511 IC_kwDOAMm_X85cNJss shoyer 1217238 2023-05-14T17:17:56Z 2023-05-14T17:17:56Z MEMBER

If we can find cases where we know concurrent writes are unsafe, we can definitely start raising errors. Better to be safe than to suffer from silent data corruption!

 
{
    "total_count": 1,
    "+1": 1,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   Appending data to a dataset stored in Zarr format produce PermissonError or NaN values in the final result 927617256
866334987 https://github.com/pydata/xarray/issues/5511#issuecomment-866334987 https://api.github.com/repos/pydata/xarray/issues/5511 MDEyOklzc3VlQ29tbWVudDg2NjMzNDk4Nw== shoyer 1217238 2021-06-22T21:08:35Z 2021-06-22T21:08:35Z MEMBER

Thanks for the report! This does look broken, which I was able to verify by running your code.

My guess is that something in Xarray's logic for appending datasets implicitly assumes that the existing datasets has been written in complete "chunks", which is not the case here.

 
{
    "total_count": 1,
    "+1": 1,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   Appending data to a dataset stored in Zarr format produce PermissonError or NaN values in the final result 927617256

Advanced export

JSON shape: default, array, newline-delimited, object

CSV options: 

CREATE TABLE [issue_comments] (
   [html_url] TEXT,
   [issue_url] TEXT,
   [id] INTEGER PRIMARY KEY,
   [node_id] TEXT,
   [user] INTEGER REFERENCES [users]([id]),
   [created_at] TEXT,
   [updated_at] TEXT,
   [author_association] TEXT,
   [body] TEXT,
   [reactions] TEXT,
   [performed_via_github_app] TEXT,
   [issue] INTEGER REFERENCES [issues]([id])
);
CREATE INDEX [idx_issue_comments_issue]
    ON [issue_comments] ([issue]);
CREATE INDEX [idx_issue_comments_user]
    ON [issue_comments] ([user]);