issue_comments
2 rows where issue = 345090013 sorted by updated_at descending
This data as json, CSV (advanced)
Suggested facets: created_at (date), updated_at (date)
issue 1
- Failing test by dask==0.18.2 · 2 ✖
id | html_url | issue_url | node_id | user | created_at | updated_at ▲ | author_association | body | reactions | performed_via_github_app | issue |
---|---|---|---|---|---|---|---|---|---|---|---|
417699273 | https://github.com/pydata/xarray/issues/2318#issuecomment-417699273 | https://api.github.com/repos/pydata/xarray/issues/2318 | MDEyOklzc3VlQ29tbWVudDQxNzY5OTI3Mw== | shoyer 1217238 | 2018-08-31T15:25:11Z | 2018-08-31T15:25:11Z | MEMBER | Actually, it turns up for another dtype with the same test. Details to follow in a new dask issue. |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
Failing test by dask==0.18.2 345090013 | |
417698914 | https://github.com/pydata/xarray/issues/2318#issuecomment-417698914 | https://api.github.com/repos/pydata/xarray/issues/2318 | MDEyOklzc3VlQ29tbWVudDQxNzY5ODkxNA== | shoyer 1217238 | 2018-08-31T15:23:53Z | 2018-08-31T15:23:53Z | MEMBER | This has resurfaced... I marked the test as xfail on 0.18.2, but didn't verify that my fix for the dask issue actually fixed this :( |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
Failing test by dask==0.18.2 345090013 |
Advanced export
JSON shape: default, array, newline-delimited, object
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]);
user 1