issue_comments

Table actions

1 row where author_association = "CONTRIBUTOR" and issue = 619347681 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

issue 1

  • utility function to save complex values as a netCDF file · 1 ✖

author_association 1

  • CONTRIBUTOR · 1 ✖
id html_url issue_url node_id user created_at updated_at ▲ author_association body reactions performed_via_github_app issue
633251217 https://github.com/pydata/xarray/issues/4068#issuecomment-633251217 https://api.github.com/repos/pydata/xarray/issues/4068 MDEyOklzc3VlQ29tbWVudDYzMzI1MTIxNw== DWesl 22566757 2020-05-24T15:53:10Z 2020-05-24T15:53:10Z CONTRIBUTOR

For others reading this issue, the h5netcdf workaround was discussed in #3297, with further discussion on supporting complex numbers in netCDF in cf-convention/cf-conventions#204.

The short version: engine="h5netcdf", invalid_netcdf=True will save these files, but the netCDF-C library doesn't understand the result. Reading with engine="h5netcdf" may be able to round-trip these files, but I haven't checked that.

There is a longer discussion of why netCDF-C doesn't understand these files at Unidata/netcdf-c#267. That specific issue is for booleans, but complex numbers are likely the same.

 
{
    "total_count": 1,
    "+1": 1,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   utility function to save complex values as a netCDF file 619347681

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