issue_comments
3 rows where issue = 768981497 and user = 10194086 sorted by updated_at descending
This data as json, CSV (advanced)
Suggested facets: reactions, created_at (date), updated_at (date)
issue 1
- Raise an informative error message when object array has mixed types · 3 ✖
| id | html_url | issue_url | node_id | user | created_at | updated_at ▲ | author_association | body | reactions | performed_via_github_app | issue |
|---|---|---|---|---|---|---|---|---|---|---|---|
| 765655950 | https://github.com/pydata/xarray/pull/4700#issuecomment-765655950 | https://api.github.com/repos/pydata/xarray/issues/4700 | MDEyOklzc3VlQ29tbWVudDc2NTY1NTk1MA== | mathause 10194086 | 2021-01-22T20:08:54Z | 2021-01-22T20:08:54Z | MEMBER | No I wouldn't subsample. With normal use case I meant saving legitimate object arrays. I am not sure how often they occur in the wild. |
{
"total_count": 0,
"+1": 0,
"-1": 0,
"laugh": 0,
"hooray": 0,
"confused": 0,
"heart": 0,
"rocket": 0,
"eyes": 0
} |
Raise an informative error message when object array has mixed types 768981497 | |
| 764932215 | https://github.com/pydata/xarray/pull/4700#issuecomment-764932215 | https://api.github.com/repos/pydata/xarray/issues/4700 | MDEyOklzc3VlQ29tbWVudDc2NDkzMjIxNQ== | mathause 10194086 | 2021-01-21T20:52:18Z | 2021-01-21T20:52:18Z | MEMBER | Yes, I'd say go ahead. (I just hope it's not too big of a performance hit for normal use cases.) |
{
"total_count": 0,
"+1": 0,
"-1": 0,
"laugh": 0,
"hooray": 0,
"confused": 0,
"heart": 0,
"rocket": 0,
"eyes": 0
} |
Raise an informative error message when object array has mixed types 768981497 | |
| 747296742 | https://github.com/pydata/xarray/pull/4700#issuecomment-747296742 | https://api.github.com/repos/pydata/xarray/issues/4700 | MDEyOklzc3VlQ29tbWVudDc0NzI5Njc0Mg== | mathause 10194086 | 2020-12-17T08:40:57Z | 2020-12-17T08:40:57Z | MEMBER | It took around 40 s for an array of 10**9 elements. That would be around 150 years of daily data (180*360*150*365). I am not sure though how much sense it makes to have such a large array with object dtype. Also an array of this size is likely a dask array and there is already a performance warning on this. So I'd say go ahead. |
{
"total_count": 1,
"+1": 1,
"-1": 0,
"laugh": 0,
"hooray": 0,
"confused": 0,
"heart": 0,
"rocket": 0,
"eyes": 0
} |
Raise an informative error message when object array has mixed types 768981497 |
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