issue_comments
2 rows where issue = 904153867 and user = 2448579 sorted by updated_at descending
This data as json, CSV (advanced)
issue 1
- Improvements to lazy behaviour of `xr.cov()` and `xr.corr()` · 2 ✖
id | html_url | issue_url | node_id | user | created_at | updated_at ▲ | author_association | body | reactions | performed_via_github_app | issue |
---|---|---|---|---|---|---|---|---|---|---|---|
850650732 | https://github.com/pydata/xarray/pull/5390#issuecomment-850650732 | https://api.github.com/repos/pydata/xarray/issues/5390 | MDEyOklzc3VlQ29tbWVudDg1MDY1MDczMg== | dcherian 2448579 | 2021-05-28T20:19:56Z | 2021-05-28T20:20:52Z | MEMBER |
This second term looks very weird to me, it should be a no-op
is it just
|
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
Improvements to lazy behaviour of `xr.cov()` and `xr.corr()` 904153867 | |
850535282 | https://github.com/pydata/xarray/pull/5390#issuecomment-850535282 | https://api.github.com/repos/pydata/xarray/issues/5390 | MDEyOklzc3VlQ29tbWVudDg1MDUzNTI4Mg== | dcherian 2448579 | 2021-05-28T16:31:36Z | 2021-05-28T16:31:36Z | MEMBER | @AndrewWilliams3142 I think that's right. You can confirm these ideas by profiling a test problem: https://docs.dask.org/en/latest/diagnostics-local.html#example It does seem like with the new version dask will hold on on to |
{ "total_count": 1, "+1": 1, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
Improvements to lazy behaviour of `xr.cov()` and `xr.corr()` 904153867 |
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