issue_comments

Table actions

where author_association = "MEMBER", issue = 408426920 and user = 1217238 sorted by updated_at descending

✎ View and edit SQL

This data as json, CSV (advanced)

These facets timed out: author_association, issue

user 1

  • shoyer · 1 ✖
id html_url issue_url node_id user created_at updated_at ▲ author_association body reactions performed_via_github_app issue
462096025 https://github.com/pydata/xarray/issues/2758#issuecomment-462096025 https://api.github.com/repos/pydata/xarray/issues/2758 MDEyOklzc3VlQ29tbWVudDQ2MjA5NjAyNQ== shoyer 1217238 2019-02-10T01:45:38Z 2019-02-10T01:45:38Z MEMBER

The source of your trouble is that the time variable on ds_test2 doesn't have datetime64 type, so xarray isn't making use of the units encoding. Xarray is giving an error message rather than silently ignoring units.

There's also definitely an opportunity for better error messages here, but the work around is to either let xarray handle datetime conversion or do it all yourself by not including units in encoding.

 
{
    "total_count": 1,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 1,
    "rocket": 0,
    "eyes": 0
}
   Dataset.to_netcdf() results in unexpected encoding parameters for 'netCDF4' backend 408426920

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