issue_comments
where issue = 480753417 and user = 2448579 sorted by updated_at descending
This data as json, CSV (advanced)
These facets timed out: author_association, issue
| id | html_url | issue_url | node_id | user | created_at | updated_at ▲ | author_association | body | reactions | performed_via_github_app | issue |
|---|---|---|---|---|---|---|---|---|---|---|---|
| 870915351 | https://github.com/pydata/xarray/issues/3216#issuecomment-870915351 | https://api.github.com/repos/pydata/xarray/issues/3216 | MDEyOklzc3VlQ29tbWVudDg3MDkxNTM1MQ== | dcherian 2448579 | 2021-06-29T21:03:27Z | 2021-06-29T21:03:27Z | MEMBER | @hCraker that's not right. rolling works by using fixed length windows so what you are doing only works with evenly spaced data. What's being discussed here is rolling with windows of varying lengths. I don't know how to do that efficiently. |
{
"total_count": 0,
"+1": 0,
"-1": 0,
"laugh": 0,
"hooray": 0,
"confused": 0,
"heart": 0,
"rocket": 0,
"eyes": 0
} |
Feature request: time-based rolling window functionality 480753417 | |
| 521303238 | https://github.com/pydata/xarray/issues/3216#issuecomment-521303238 | https://api.github.com/repos/pydata/xarray/issues/3216 | MDEyOklzc3VlQ29tbWVudDUyMTMwMzIzOA== | dcherian 2448579 | 2019-08-14T15:47:04Z | 2019-08-14T15:47:04Z | MEMBER | Does |
{
"total_count": 0,
"+1": 0,
"-1": 0,
"laugh": 0,
"hooray": 0,
"confused": 0,
"heart": 0,
"rocket": 0,
"eyes": 0
} |
Feature request: time-based rolling window functionality 480753417 |
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