issue_comments
2 rows where issue = 663977922 and user = 14808389 sorted by updated_at descending
This data as json, CSV (advanced)
Suggested facets: created_at (date), updated_at (date)
issue 1
- fix the RTD timeouts · 2 ✖
| id | html_url | issue_url | node_id | user | created_at | updated_at ▲ | author_association | body | reactions | performed_via_github_app | issue |
|---|---|---|---|---|---|---|---|---|---|---|---|
| 662699356 | https://github.com/pydata/xarray/pull/4254#issuecomment-662699356 | https://api.github.com/repos/pydata/xarray/issues/4254 | MDEyOklzc3VlQ29tbWVudDY2MjY5OTM1Ng== | keewis 14808389 | 2020-07-22T21:12:35Z | 2020-07-22T21:12:35Z | MEMBER | that seems to have worked, too, so this should be ready for merging. |
{
"total_count": 0,
"+1": 0,
"-1": 0,
"laugh": 0,
"hooray": 0,
"confused": 0,
"heart": 0,
"rocket": 0,
"eyes": 0
} |
fix the RTD timeouts 663977922 | |
| 662685011 | https://github.com/pydata/xarray/pull/4254#issuecomment-662685011 | https://api.github.com/repos/pydata/xarray/issues/4254 | MDEyOklzc3VlQ29tbWVudDY2MjY4NTAxMQ== | keewis 14808389 | 2020-07-22T20:40:40Z | 2020-07-22T20:40:40Z | MEMBER | okay, so with this my own setup passes, but the PR build seems to have had a hiccup (it's still running, though). We need to remember to revert this PR once pandas-dev/pandas#35361 has been merged and a new |
{
"total_count": 0,
"+1": 0,
"-1": 0,
"laugh": 0,
"hooray": 0,
"confused": 0,
"heart": 0,
"rocket": 0,
"eyes": 0
} |
fix the RTD timeouts 663977922 |
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