issue_comments

Table actions

1 row where issue = 279883145 and user = 1217238 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

  • shoyer · 1 ✖

issue 1

  • .groupby_bins fails when data is not contained in bins · 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
350077724 https://github.com/pydata/xarray/issues/1764#issuecomment-350077724 https://api.github.com/repos/pydata/xarray/issues/1764 MDEyOklzc3VlQ29tbWVudDM1MDA3NzcyNA== shoyer 1217238 2017-12-07T19:59:16Z 2017-12-07T19:59:16Z MEMBER

I agree, this behavior is not so useful. It appears that our current groupby_bins logic fails with an error if none of the data falls in the bins.

I'll mark this as a bug. It could be a little tricky to fix because our current logic in GroupBy.apply() (used by .sum() indirectly) looks at one result to figure out how to stack grouped results. But at the very least we should raise a more helpful error message.

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   .groupby_bins fails when data is not contained in bins 279883145

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