issue_comments
5 rows where author_association = "NONE" and issue = 95114700 sorted by updated_at descending
This data as json, CSV (advanced)
Suggested facets: created_at (date), updated_at (date)
issue 1
- API design for pointwise indexing · 5 ✖
id | html_url | issue_url | node_id | user | created_at | updated_at ▲ | author_association | body | reactions | performed_via_github_app | issue |
---|---|---|---|---|---|---|---|---|---|---|---|
564105235 | https://github.com/pydata/xarray/issues/475#issuecomment-564105235 | https://api.github.com/repos/pydata/xarray/issues/475 | MDEyOklzc3VlQ29tbWVudDU2NDEwNTIzNQ== | stale[bot] 26384082 | 2019-12-10T16:07:34Z | 2019-12-10T16:07:34Z | NONE | In order to maintain a list of currently relevant issues, we mark issues as stale after a period of inactivity If this issue remains relevant, please comment here or remove the |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
API design for pointwise indexing 95114700 | |
355243617 | https://github.com/pydata/xarray/issues/475#issuecomment-355243617 | https://api.github.com/repos/pydata/xarray/issues/475 | MDEyOklzc3VlQ29tbWVudDM1NTI0MzYxNw== | stefanomattia 16152387 | 2018-01-04T10:04:05Z | 2018-01-04T10:04:05Z | NONE | That post must look a bit amateurish, I reckon, but if you guys think it could be a starting point for a KD-tree search implementation in xarray, I would be thrilled to contribute! There is no learning without trying, after all. I could start from https://github.com/pydata/xarray/issues/475#issuecomment-125349079. @jhamman maybe you could send me an email with a few requirements? |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
API design for pointwise indexing 95114700 | |
354967495 | https://github.com/pydata/xarray/issues/475#issuecomment-354967495 | https://api.github.com/repos/pydata/xarray/issues/475 | MDEyOklzc3VlQ29tbWVudDM1NDk2NzQ5NQ== | stefanomattia 16152387 | 2018-01-03T09:23:47Z | 2018-01-03T09:23:47Z | NONE | Thanks @jhamman, I'd love to contribute! I'm not that confident in my Python skills, but maybe with a little guidance? Let me know if or how I could help. |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
API design for pointwise indexing 95114700 | |
121790688 | https://github.com/pydata/xarray/issues/475#issuecomment-121790688 | https://api.github.com/repos/pydata/xarray/issues/475 | MDEyOklzc3VlQ29tbWVudDEyMTc5MDY4OA== | wholmgren 4383303 | 2015-07-16T00:42:08Z | 2015-07-16T00:42:08Z | NONE | Unidata also has a blog post benchmarking cKDTree and other methods and concludes "Your Mileage May Vary". I'd probably just go with a KDTree, but something to aware of. |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
API design for pointwise indexing 95114700 | |
121701139 | https://github.com/pydata/xarray/issues/475#issuecomment-121701139 | https://api.github.com/repos/pydata/xarray/issues/475 | MDEyOklzc3VlQ29tbWVudDEyMTcwMTEzOQ== | wholmgren 4383303 | 2015-07-15T18:15:49Z | 2015-07-15T18:15:49Z | NONE | Seems like if your method is going to be named One thing to keep in mind is that for many of us the "nearest-neighbor" part isn't really |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
API design for pointwise indexing 95114700 |
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 3