issue_comments
9 rows where author_association = "MEMBER", issue = 655389649 and user = 6815844 sorted by updated_at descending
This data as json, CSV (advanced)
Suggested facets: reactions, created_at (date), updated_at (date)
issue 1
- nd-rolling · 9 ✖
id | html_url | issue_url | node_id | user | created_at | updated_at ▲ | author_association | body | reactions | performed_via_github_app | issue |
---|---|---|---|---|---|---|---|---|---|---|---|
670821295 | https://github.com/pydata/xarray/pull/4219#issuecomment-670821295 | https://api.github.com/repos/pydata/xarray/issues/4219 | MDEyOklzc3VlQ29tbWVudDY3MDgyMTI5NQ== | fujiisoup 6815844 | 2020-08-08T04:18:08Z | 2020-08-08T04:18:08Z | MEMBER | @max-sixty thanks for the review. merged |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
nd-rolling 655389649 | |
670705764 | https://github.com/pydata/xarray/pull/4219#issuecomment-670705764 | https://api.github.com/repos/pydata/xarray/issues/4219 | MDEyOklzc3VlQ29tbWVudDY3MDcwNTc2NA== | fujiisoup 6815844 | 2020-08-07T20:45:01Z | 2020-08-07T20:45:01Z | MEMBER | Thanks @max-sixty . You are completely correct. As the test pass, I was fooling myself. The reason was that the dataset I was using for the test does not have Fixed. Now it correctly fails for |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
nd-rolling 655389649 | |
667411555 | https://github.com/pydata/xarray/pull/4219#issuecomment-667411555 | https://api.github.com/repos/pydata/xarray/issues/4219 | MDEyOklzc3VlQ29tbWVudDY2NzQxMTU1NQ== | fujiisoup 6815844 | 2020-07-31T22:25:25Z | 2020-07-31T22:25:25Z | MEMBER | Thanks @max-sixty for the review ;) I'll work for the update in a few days. |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
nd-rolling 655389649 | |
666841275 | https://github.com/pydata/xarray/pull/4219#issuecomment-666841275 | https://api.github.com/repos/pydata/xarray/issues/4219 | MDEyOklzc3VlQ29tbWVudDY2Njg0MTI3NQ== | fujiisoup 6815844 | 2020-07-31T00:42:23Z | 2020-07-31T00:42:23Z | MEMBER | Could anyone kindly review this? |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
nd-rolling 655389649 | |
658403527 | https://github.com/pydata/xarray/pull/4219#issuecomment-658403527 | https://api.github.com/repos/pydata/xarray/issues/4219 | MDEyOklzc3VlQ29tbWVudDY1ODQwMzUyNw== | fujiisoup 6815844 | 2020-07-14T20:44:12Z | 2020-07-14T20:44:12Z | MEMBER | I got an error for typechecking, only in CI but not in local, from the code that I didn't change. |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
nd-rolling 655389649 | |
657902895 | https://github.com/pydata/xarray/pull/4219#issuecomment-657902895 | https://api.github.com/repos/pydata/xarray/issues/4219 | MDEyOklzc3VlQ29tbWVudDY1NzkwMjg5NQ== | fujiisoup 6815844 | 2020-07-14T00:49:38Z | 2020-07-14T00:49:38Z | MEMBER | A possible improvement will be nan-reduction methods for nd-rolling. Currently, we just use numpy nan-reductions, which is memory consuming for strided arrays. This issue can be solved by replacing nan by appropriate values and applying nonnan-reduction methods,
e.g.,
I'd like to leave this improvement to future PR. |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
nd-rolling 655389649 | |
657897529 | https://github.com/pydata/xarray/pull/4219#issuecomment-657897529 | https://api.github.com/repos/pydata/xarray/issues/4219 | MDEyOklzc3VlQ29tbWVudDY1Nzg5NzUyOQ== | fujiisoup 6815844 | 2020-07-14T00:27:51Z | 2020-07-14T00:27:51Z | MEMBER | I think now it is ready for review, though I'm sure tests miss a lot of edge cases. Maybe we can fix them if pointed out. |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
nd-rolling 655389649 | |
657270068 | https://github.com/pydata/xarray/pull/4219#issuecomment-657270068 | https://api.github.com/repos/pydata/xarray/issues/4219 | MDEyOklzc3VlQ29tbWVudDY1NzI3MDA2OA== | fujiisoup 6815844 | 2020-07-12T20:18:28Z | 2020-07-12T20:18:28Z | MEMBER | Another API concern. We now use With nd-dimension, I think Even if we leave it, we may disallow nd-argument of |
{ "total_count": 1, "+1": 1, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
nd-rolling 655389649 | |
657269189 | https://github.com/pydata/xarray/pull/4219#issuecomment-657269189 | https://api.github.com/repos/pydata/xarray/issues/4219 | MDEyOklzc3VlQ29tbWVudDY1NzI2OTE4OQ== | fujiisoup 6815844 | 2020-07-12T20:09:34Z | 2020-07-12T20:09:34Z | MEMBER | Hi @max-sixty
I couldn't think of it until just now. But yes, it sounds to me like a repeated rolling operation.
No. With nd-rolling, we need to use numpy reductions.
Its |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
nd-rolling 655389649 |
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