issue_comments
1 row where issue = 1280507371 and user = 3383837 sorted by updated_at descending
This data as json, CSV (advanced)
Suggested facets: created_at (date), updated_at (date)
issue 1
- `xr.open_rasterio` fails to locate file after being ran 3 times · 1 ✖
id | html_url | issue_url | node_id | user | created_at | updated_at ▲ | author_association | body | reactions | performed_via_github_app | issue |
---|---|---|---|---|---|---|---|---|---|---|---|
1424713396 | https://github.com/pydata/xarray/issues/6715#issuecomment-1424713396 | https://api.github.com/repos/pydata/xarray/issues/6715 | IC_kwDOAMm_X85U62a0 | itcarroll 3383837 | 2023-02-09T19:38:17Z | 2023-02-09T19:38:17Z | CONTRIBUTOR | @ShengpeiWang Has the right preventative solution. What do you do when you mess this up in an interactive python session? I can find no way to unlock the file other than renaming it and then opening and closing. The lock even persists through restarting the python interpreter. |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
`xr.open_rasterio` fails to locate file after being ran 3 times 1280507371 |
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