issue_comments
2 rows where author_association = "MEMBER", issue = 1420230433 and user = 14808389 sorted by updated_at descending
This data as json, CSV (advanced)
issue 1
- Avoid loading any data for reprs · 2 ✖
| id | html_url | issue_url | node_id | user | created_at | updated_at ▲ | author_association | body | reactions | performed_via_github_app | issue |
|---|---|---|---|---|---|---|---|---|---|---|---|
| 1289198558 | https://github.com/pydata/xarray/pull/7203#issuecomment-1289198558 | https://api.github.com/repos/pydata/xarray/issues/7203 | IC_kwDOAMm_X85M15ve | keewis 14808389 | 2022-10-24T15:18:53Z | 2022-10-24T15:18:53Z | MEMBER | right, this seems to be an old (but unfortunately still unfixed) issue in |
{
"total_count": 1,
"+1": 1,
"-1": 0,
"laugh": 0,
"hooray": 0,
"confused": 0,
"heart": 0,
"rocket": 0,
"eyes": 0
} |
Avoid loading any data for reprs 1420230433 | |
| 1288939892 | https://github.com/pydata/xarray/pull/7203#issuecomment-1288939892 | https://api.github.com/repos/pydata/xarray/issues/7203 | IC_kwDOAMm_X85M06l0 | keewis 14808389 | 2022-10-24T12:10:45Z | 2022-10-24T12:53:36Z | MEMBER | FWIW, I think the issue is not unix vs windows but 32bit OS vs 64bit OS. In any case, if we want to be consistent I guess we have to specify the dtype explicitly? So instead of |
{
"total_count": 0,
"+1": 0,
"-1": 0,
"laugh": 0,
"hooray": 0,
"confused": 0,
"heart": 0,
"rocket": 0,
"eyes": 0
} |
Avoid loading any data for reprs 1420230433 |
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