issue_comments

Table actions

1 row where issue = 302679890 and user = 12229877 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

  • Zac-HD · 1 ✖

issue 1

  • imshow should work with third dimension of len 1 · 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
370774614 https://github.com/pydata/xarray/issues/1966#issuecomment-370774614 https://api.github.com/repos/pydata/xarray/issues/1966 MDEyOklzc3VlQ29tbWVudDM3MDc3NDYxNA== Zac-HD 12229877 2018-03-06T13:04:03Z 2018-03-06T13:08:54Z CONTRIBUTOR

Ugh, this is literally a one-line fix: I shouldn't have put .squeeze() here. If you also ensure that the dtype is OK (specify uint8, or divide by nine) the example then works.

It's also exactly the kind of thing that Hypothesis would catch for us via #1846. Work (moved to less coding :cry:) and the upcoming major release of Hypothesis have priority, but I'll try to find time.

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   imshow should work with third dimension of len 1 302679890

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