issue_comments
2 rows where issue = 1730451312 sorted by updated_at descending
This data as json, CSV (advanced)
Suggested facets: created_at (date), updated_at (date)
issue 1
- occasional segfaults on CI · 2 ✖
id | html_url | issue_url | node_id | user | created_at | updated_at ▲ | author_association | body | reactions | performed_via_github_app | issue |
---|---|---|---|---|---|---|---|---|---|---|---|
1567366415 | https://github.com/pydata/xarray/issues/7879#issuecomment-1567366415 | https://api.github.com/repos/pydata/xarray/issues/7879 | IC_kwDOAMm_X85dbB0P | keewis 14808389 | 2023-05-29T17:22:09Z | 2023-05-29T17:22:09Z | MEMBER | If I'm reading the different issues correctly, that means this is a duplicate of #7079 |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
occasional segfaults on CI 1730451312 | |
1567319929 | https://github.com/pydata/xarray/issues/7879#issuecomment-1567319929 | https://api.github.com/repos/pydata/xarray/issues/7879 | IC_kwDOAMm_X85da2d5 | huard 81219 | 2023-05-29T16:15:49Z | 2023-05-29T16:15:49Z | CONTRIBUTOR | There are similar segfaults in an xncml PR: https://github.com/xarray-contrib/xncml/pull/48 Googling around suggest it is related to netCDF not being thread-safe and recent python-netcdf4 releasing the GIL. |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
occasional segfaults on CI 1730451312 |
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 2