issue_comments

Table actions

1 row where issue = 145807529 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 · 1 ✖

issue 1

  • opendap and gzipped files · 1 ✖

author_association 1

id html_url issue_url node_id user created_at updated_at ▲ author_association body reactions performed_via_github_app issue
205524524 https://github.com/pydata/xarray/issues/816#issuecomment-205524524 https://api.github.com/repos/pydata/xarray/issues/816 MDEyOklzc3VlQ29tbWVudDIwNTUyNDUyNA== shoyer 1217238 2016-04-04T22:38:54Z 2016-04-04T22:38:54Z MEMBER

Yes, this is a bug in how xarray dispatches to backends.

We should check for remote URIs (e.g., with is_remote_uri) before checking for the .gz file extension: https://github.com/pydata/xarray/blob/master/xarray/backends/api.py#L190

Any interest in putting together a PR with a fix?

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   opendap and gzipped files 145807529

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