issue_comments

Table actions

1 row where issue = 301888608 and user = 2443309 sorted by updated_at descending

✎ View and edit SQL

This data as json, CSV (advanced)

These facets timed out: author_association, issue

user 1

  • jhamman · 1 ✖
id html_url issue_url node_id user created_at updated_at ▲ author_association body reactions performed_via_github_app issue
370043488 https://github.com/pydata/xarray/issues/1954#issuecomment-370043488 https://api.github.com/repos/pydata/xarray/issues/1954 MDEyOklzc3VlQ29tbWVudDM3MDA0MzQ4OA== jhamman 2443309 2018-03-02T20:29:49Z 2018-03-02T20:29:49Z MEMBER

Okay, this is just a little messy right now because we're ahead of zarr in their release schedule. We expect that will come out on Monday (see https://github.com/zarr-developers/zarr/issues/242).

Typically, we have stayed away from checking versions of all optional dependencies on import this may be one time that would be useful. The problem is these checks often fall out of date end up causing unnecessary clutter down the line.

To resolve this we can add a version check (as you've shown above) or we can wait until Monday. I'm also not opposed to mentioning in the documentation what minimum version we support is. 

{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   ds.to_zarr error on creation 301888608

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