issue_comments
2 rows where author_association = "MEMBER", issue = 1333650265 and user = 5635139 sorted by updated_at descending
This data as json, CSV (advanced)
Suggested facets: created_at (date), updated_at (date)
issue 1
- `sel` behaving randomly when applying to a dataset with multiprocessing · 2 ✖
id | html_url | issue_url | node_id | user | created_at | updated_at ▲ | author_association | body | reactions | performed_via_github_app | issue |
---|---|---|---|---|---|---|---|---|---|---|---|
1210216148 | https://github.com/pydata/xarray/issues/6904#issuecomment-1210216148 | https://api.github.com/repos/pydata/xarray/issues/6904 | IC_kwDOAMm_X85IIm7U | max-sixty 5635139 | 2022-08-10T06:24:54Z | 2022-08-10T06:24:54Z | MEMBER | Re nearest, does it replicate with exact lookups? |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
`sel` behaving randomly when applying to a dataset with multiprocessing 1333650265 | |
1209921400 | https://github.com/pydata/xarray/issues/6904#issuecomment-1209921400 | https://api.github.com/repos/pydata/xarray/issues/6904 | IC_kwDOAMm_X85IHe94 | max-sixty 5635139 | 2022-08-09T21:39:21Z | 2022-08-09T21:39:21Z | MEMBER | That sounds quite unfriendly! A couple of questions to reduce the size of the example, without providing any answers yet unfortunately:
|
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
`sel` behaving randomly when applying to a dataset with multiprocessing 1333650265 |
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