issue_comments
1 row where issue = 1277437106 and user = 35968931 sorted by updated_at descending
This data as json, CSV (advanced)
Suggested facets: created_at (date), updated_at (date)
issue 1
- Means of zarr arrays cause a memory overload in dask workers · 1 ✖
id | html_url | issue_url | node_id | user | created_at | updated_at ▲ | author_association | body | reactions | performed_via_github_app | issue |
---|---|---|---|---|---|---|---|---|---|---|---|
1161987610 | https://github.com/pydata/xarray/issues/6709#issuecomment-1161987610 | https://api.github.com/repos/pydata/xarray/issues/6709 | IC_kwDOAMm_X85FQoYa | TomNicholas 35968931 | 2022-06-21T16:31:58Z | 2022-06-21T16:31:58Z | MEMBER | Hi @robin-cls - can we see the dask graphs (or a representative subset of them) for these two cases? |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
Means of zarr arrays cause a memory overload in dask workers 1277437106 |
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