issue_comments

Table actions

1 row where issue = 454106835 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
504796468 https://github.com/pydata/xarray/issues/3008#issuecomment-504796468 https://api.github.com/repos/pydata/xarray/issues/3008 MDEyOklzc3VlQ29tbWVudDUwNDc5NjQ2OA== shoyer 1217238 2019-06-23T23:18:08Z 2019-06-23T23:18:08Z MEMBER

I agree, this is definitely not ideal behavior!

I hesitate to call it a bug only because I'm not sure if we've ever supported this behavior.

It would be nice to fix this, and I would encourage you (or other interested users) to look into it.

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   to_dataframe/to_series fails when one out of more than one dims are stacked / multiindex 454106835

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