issue_comments
2 rows where issue = 1316423844 sorted by updated_at descending
This data as json, CSV (advanced)
Suggested facets: created_at (date), updated_at (date)
issue 1
- RuntimeError when formatting sparse-backed DataArray in f-string · 2 ✖
| id | html_url | issue_url | node_id | user | created_at | updated_at ▲ | author_association | body | reactions | performed_via_github_app | issue |
|---|---|---|---|---|---|---|---|---|---|---|---|
| 1209127586 | https://github.com/pydata/xarray/issues/6822#issuecomment-1209127586 | https://api.github.com/repos/pydata/xarray/issues/6822 | IC_kwDOAMm_X85IEdKi | khaeru 1634164 | 2022-08-09T09:17:39Z | 2022-08-09T09:17:39Z | NONE | Thanks @Illviljan for the fix! 🙏🏾 |
{
"total_count": 0,
"+1": 0,
"-1": 0,
"laugh": 0,
"hooray": 0,
"confused": 0,
"heart": 0,
"rocket": 0,
"eyes": 0
} |
RuntimeError when formatting sparse-backed DataArray in f-string 1316423844 | |
| 1193828381 | https://github.com/pydata/xarray/issues/6822#issuecomment-1193828381 | https://api.github.com/repos/pydata/xarray/issues/6822 | IC_kwDOAMm_X85HKGAd | Illviljan 14371165 | 2022-07-25T09:49:34Z | 2022-07-25T09:49:34Z | MEMBER | This comes from #5981, I think it's better to just let the backend array (numpy, dask, sparse etc.) determine how to handle string formatting instead of forcing to numpy arrays. |
{
"total_count": 0,
"+1": 0,
"-1": 0,
"laugh": 0,
"hooray": 0,
"confused": 0,
"heart": 0,
"rocket": 0,
"eyes": 0
} |
RuntimeError when formatting sparse-backed DataArray in f-string 1316423844 |
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