issue_comments
4 rows where author_association = "MEMBER" and issue = 480753417 sorted by updated_at descending
This data as json, CSV (advanced)
Suggested facets: created_at (date), updated_at (date)
issue 1
- Feature request: time-based rolling window functionality · 4 ✖
id | html_url | issue_url | node_id | user | created_at | updated_at ▲ | author_association | body | reactions | performed_via_github_app | issue |
---|---|---|---|---|---|---|---|---|---|---|---|
871665765 | https://github.com/pydata/xarray/issues/3216#issuecomment-871665765 | https://api.github.com/repos/pydata/xarray/issues/3216 | MDEyOklzc3VlQ29tbWVudDg3MTY2NTc2NQ== | max-sixty 5635139 | 2021-06-30T19:21:38Z | 2021-06-30T19:21:38Z | MEMBER | Pandas has this, so it's not intractable. If you'd like the feature, add a 👍 to the issue or help it along by looking at what would be required / starting an implementation. |
{ "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 | |
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 | |
618050489 | https://github.com/pydata/xarray/issues/3216#issuecomment-618050489 | https://api.github.com/repos/pydata/xarray/issues/3216 | MDEyOklzc3VlQ29tbWVudDYxODA1MDQ4OQ== | max-sixty 5635139 | 2020-04-22T21:28:59Z | 2020-04-22T21:28:59Z | MEMBER | We would definitely take a PR for this; and it might not be that difficult given it's already implemented in pandas. |
{ "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 2