issue_comments
2 rows where issue = 1030492705 and user = 14808389 sorted by updated_at descending
This data as json, CSV (advanced)
issue 1
- _season_from_months can now handle np.nan · 2 ✖
| id | html_url | issue_url | node_id | user | created_at | updated_at ▲ | author_association | body | reactions | performed_via_github_app | issue |
|---|---|---|---|---|---|---|---|---|---|---|---|
| 1008380806 | https://github.com/pydata/xarray/pull/5876#issuecomment-1008380806 | https://api.github.com/repos/pydata/xarray/issues/5876 | IC_kwDOAMm_X848GquG | keewis 14808389 | 2022-01-09T20:37:08Z | 2022-01-09T20:37:08Z | MEMBER | I agree. For now, it would be good to use The only way to really fix this would be to introduce missing values for string dtypes, but I guess that will still take a while (unless we get |
{
"total_count": 1,
"+1": 1,
"-1": 0,
"laugh": 0,
"hooray": 0,
"confused": 0,
"heart": 0,
"rocket": 0,
"eyes": 0
} |
_season_from_months can now handle np.nan 1030492705 | |
| 957894785 | https://github.com/pydata/xarray/pull/5876#issuecomment-957894785 | https://api.github.com/repos/pydata/xarray/issues/5876 | IC_kwDOAMm_X845GFCB | keewis 14808389 | 2021-11-02T16:12:17Z | 2021-11-02T16:12:17Z | MEMBER | that's a random error that sometimes happens with |
{
"total_count": 1,
"+1": 1,
"-1": 0,
"laugh": 0,
"hooray": 0,
"confused": 0,
"heart": 0,
"rocket": 0,
"eyes": 0
} |
_season_from_months can now handle np.nan 1030492705 |
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