issue_comments

Table actions

1 row where issue = 417542619 and user = 2443309 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

  • jhamman · 1 ✖

issue 1

  • Test failure with TestValidateAttrs.test_validating_attrs · 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
472034107 https://github.com/pydata/xarray/issues/2803#issuecomment-472034107 https://api.github.com/repos/pydata/xarray/issues/2803 MDEyOklzc3VlQ29tbWVudDQ3MjAzNDEwNw== jhamman 2443309 2019-03-12T14:53:11Z 2019-03-12T14:53:11Z MEMBER

@shoyer - I'm surprised we had a test for this behavior. Based on https://github.com/Unidata/netcdf4-python/issues/841, it seems we don't want this behavior to work. Can we just remove this test (or better yet, insure the ValueError is raised)? 

{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   Test failure with TestValidateAttrs.test_validating_attrs 417542619

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