issue_comments

Table actions

1 row where author_association = "MEMBER", issue = 1416709246 and user = 2448579 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

  • dcherian · 1 ✖

issue 1

  • Cannot Save NetCDF: Conflicting _FillValue and Missing_Value · 1 ✖

author_association 1

  • MEMBER · 1 ✖
id html_url issue_url node_id user created_at updated_at ▲ author_association body reactions performed_via_github_app issue
1287124949 https://github.com/pydata/xarray/issues/7191#issuecomment-1287124949 https://api.github.com/repos/pydata/xarray/issues/7191 IC_kwDOAMm_X85Mt_fV dcherian 2448579 2022-10-21T15:30:10Z 2022-10-21T15:30:35Z MEMBER

I'm also not sure why _FillValue and missing_value should be required to have the same value.

Xarray has only one way to represent both concepts: np.nan. So when you decode you lose information on whether a value was a missing_value or _FillValue. Then when you encode, you have to pick either _FillValue or missing_value to represent the np.nan

to_netcdf will assign '_FillValue': nan.

This seems like a bug. Can you open a new issue with a minimum reproducible example that uses random data please?

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   Cannot Save NetCDF: Conflicting _FillValue and Missing_Value  1416709246

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]);