issue_comments
2 rows where issue = 523438384 and user = 10194086 sorted by updated_at descending
This data as json, CSV (advanced)
Suggested facets: created_at (date), updated_at (date)
issue 1
- Numpy 1.18 support · 2 ✖
| id | html_url | issue_url | node_id | user | created_at | updated_at ▲ | author_association | body | reactions | performed_via_github_app | issue |
|---|---|---|---|---|---|---|---|---|---|---|---|
| 554485350 | https://github.com/pydata/xarray/pull/3537#issuecomment-554485350 | https://api.github.com/repos/pydata/xarray/issues/3537 | MDEyOklzc3VlQ29tbWVudDU1NDQ4NTM1MA== | mathause 10194086 | 2019-11-15T18:57:01Z | 2019-11-15T18:57:01Z | MEMBER | Ok, thanks for the clarification. |
{
"total_count": 0,
"+1": 0,
"-1": 0,
"laugh": 0,
"hooray": 0,
"confused": 0,
"heart": 0,
"rocket": 0,
"eyes": 0
} |
Numpy 1.18 support 523438384 | |
| 554355882 | https://github.com/pydata/xarray/pull/3537#issuecomment-554355882 | https://api.github.com/repos/pydata/xarray/issues/3537 | MDEyOklzc3VlQ29tbWVudDU1NDM1NTg4Mg== | mathause 10194086 | 2019-11-15T13:20:16Z | 2019-11-15T13:20:16Z | MEMBER | Given https://github.com/numpy/numpy/pull/14841 - is this worth the extra complexity? Currently xarray is only broken wrt numpy master and there is a chance https://github.com/numpy/numpy/pull/14841 gets into 1.18 - then we could just use Also - is this the only place of |
{
"total_count": 0,
"+1": 0,
"-1": 0,
"laugh": 0,
"hooray": 0,
"confused": 0,
"heart": 0,
"rocket": 0,
"eyes": 0
} |
Numpy 1.18 support 523438384 |
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