issue_comments
2 rows where issue = 1702025553 and user = 2448579 sorted by updated_at descending
This data as json, CSV (advanced)
Suggested facets: created_at (date), updated_at (date)
issue 1
- Can't open datasets with the `rasterio` engine. · 2 ✖
id | html_url | issue_url | node_id | user | created_at | updated_at ▲ | author_association | body | reactions | performed_via_github_app | issue |
---|---|---|---|---|---|---|---|---|---|---|---|
1540816942 | https://github.com/pydata/xarray/issues/7831#issuecomment-1540816942 | https://api.github.com/repos/pydata/xarray/issues/7831 | IC_kwDOAMm_X85b1wAu | dcherian 2448579 | 2023-05-09T20:02:27Z | 2023-05-09T20:02:27Z | MEMBER | I was suggesting to special-case rioxarray only just because we recently deleted the rasterio backend, and that might ease the transition. Can we do it at the top-level open-dataset when |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
Can't open datasets with the `rasterio` engine. 1702025553 | |
1540435470 | https://github.com/pydata/xarray/issues/7831#issuecomment-1540435470 | https://api.github.com/repos/pydata/xarray/issues/7831 | IC_kwDOAMm_X85b0S4O | dcherian 2448579 | 2023-05-09T15:44:55Z | 2023-05-09T15:44:55Z | MEMBER | I think this would be nice since we recently removed the rasterio backend. |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
Can't open datasets with the `rasterio` engine. 1702025553 |
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