issue_comments
2 rows where author_association = "MEMBER" and issue = 208676242 sorted by updated_at descending
This data as json, CSV (advanced)
Suggested facets: created_at (date), updated_at (date)
issue 1
- DataArray doesnt use bottleneck implementation on rolling variance · 2 ✖
id | html_url | issue_url | node_id | user | created_at | updated_at ▲ | author_association | body | reactions | performed_via_github_app | issue |
---|---|---|---|---|---|---|---|---|---|---|---|
280996747 | https://github.com/pydata/xarray/issues/1276#issuecomment-280996747 | https://api.github.com/repos/pydata/xarray/issues/1276 | MDEyOklzc3VlQ29tbWVudDI4MDk5Njc0Nw== | jhamman 2443309 | 2017-02-20T06:15:42Z | 2017-02-20T06:15:42Z | MEMBER | @shoyer and @d-chambers - Take a look at #1278. The issue here was that we had not kept up with bottleneck's improvements and in 1.1, they added |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
DataArray doesnt use bottleneck implementation on rolling variance 208676242 | |
280986202 | https://github.com/pydata/xarray/issues/1276#issuecomment-280986202 | https://api.github.com/repos/pydata/xarray/issues/1276 | MDEyOklzc3VlQ29tbWVudDI4MDk4NjIwMg== | shoyer 1217238 | 2017-02-20T04:35:45Z | 2017-02-20T04:35:45Z | MEMBER | Indeed, Looks like Maybe @jhamman recalls why we don't use bottleneck for these? |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
DataArray doesnt use bottleneck implementation on rolling variance 208676242 |
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 2