issue_comments

Table actions

1 row where author_association = "MEMBER", issue = 293830986 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
362942383 https://github.com/pydata/xarray/issues/1879#issuecomment-362942383 https://api.github.com/repos/pydata/xarray/issues/1879 MDEyOklzc3VlQ29tbWVudDM2Mjk0MjM4Mw== shoyer 1217238 2018-02-04T21:42:33Z 2018-02-04T21:42:33Z MEMBER

What about toolz used by auto_combine?

toolz should probably be listed explicitly as an optional dependencies, but I didn't bother since it's a hard dependency of dask.array, and we only use toolz in cases where dask.array is also required. (In theory, dask.array could drop its use of toolz internally, but that's unlikely to happen anytime soon.)

For instance, given a feature with multiple backends, the dependencies for the preferred backend should be recommended, whilst the others should just be suggested.

I don't think the difference between recommended and suggested dependencies is relevant for xarray. We don't have any features with multiple backends where a single backend is strictly preferred.

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   Explicit listing of optional dependencies 293830986

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