issue_comments

Table actions

1 row where issue = 546451185 and user = 14808389 sorted by updated_at descending

✎ View and edit SQL

This data as json, CSV (advanced)

Suggested facets: updated_at (date)

user 1

  • keewis · 1 ✖

issue 1

  • Add map_blocks example to docs · 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
572144220 https://github.com/pydata/xarray/pull/3667#issuecomment-572144220 https://api.github.com/repos/pydata/xarray/issues/3667 MDEyOklzc3VlQ29tbWVudDU3MjE0NDIyMA== keewis 14808389 2020-01-08T16:19:25Z 2020-01-15T00:24:03Z MEMBER

We use the upstream-dev check as a early warning system for changes in the unreleased versions of xarray's dependencies. It being the only failure usually means upstream (I guess pandas in this case) changed something, breaking some of xarray's tests.

Since this also happens in other PRs and is completely unrelated (I think we don't run doctest in CI), I'd say you can safely ignore the failure. 

{
    "total_count": 1,
    "+1": 1,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   Add map_blocks example to docs 546451185

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