issue_comments
5 rows where issue = 340316108 sorted by updated_at descending
This data as json, CSV (advanced)
Suggested facets: created_at (date), updated_at (date)
issue 1
- string coords are converted to object dtype when using MultiIndex / stacking · 5 ✖
id | html_url | issue_url | node_id | user | created_at | updated_at ▲ | author_association | body | reactions | performed_via_github_app | issue |
---|---|---|---|---|---|---|---|---|---|---|---|
1259415933 | https://github.com/pydata/xarray/issues/2280#issuecomment-1259415933 | https://api.github.com/repos/pydata/xarray/issues/2280 | IC_kwDOAMm_X85LESl9 | benbovy 4160723 | 2022-09-27T12:12:05Z | 2022-09-27T12:12:05Z | MEMBER | This is fixed in v2022.6.0. Xarray's |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
string coords are converted to object dtype when using MultiIndex / stacking 340316108 | |
469854461 | https://github.com/pydata/xarray/issues/2280#issuecomment-469854461 | https://api.github.com/repos/pydata/xarray/issues/2280 | MDEyOklzc3VlQ29tbWVudDQ2OTg1NDQ2MQ== | max-sixty 5635139 | 2019-03-05T20:58:08Z | 2019-03-05T20:58:08Z | MEMBER | { "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
string coords are converted to object dtype when using MultiIndex / stacking 340316108 | ||
469848471 | https://github.com/pydata/xarray/issues/2280#issuecomment-469848471 | https://api.github.com/repos/pydata/xarray/issues/2280 | MDEyOklzc3VlQ29tbWVudDQ2OTg0ODQ3MQ== | shoyer 1217238 | 2019-03-05T20:39:50Z | 2019-03-05T20:39:50Z | MEMBER | @max-sixty this is #2280 :) |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
string coords are converted to object dtype when using MultiIndex / stacking 340316108 | |
469846746 | https://github.com/pydata/xarray/issues/2280#issuecomment-469846746 | https://api.github.com/repos/pydata/xarray/issues/2280 | MDEyOklzc3VlQ29tbWVudDQ2OTg0Njc0Ng== | max-sixty 5635139 | 2019-03-05T20:34:26Z | 2019-03-05T20:34:26Z | MEMBER | Is this a dupe of https://github.com/pydata/xarray/issues/2280 ? |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
string coords are converted to object dtype when using MultiIndex / stacking 340316108 | |
406451785 | https://github.com/pydata/xarray/issues/2280#issuecomment-406451785 | https://api.github.com/repos/pydata/xarray/issues/2280 | MDEyOklzc3VlQ29tbWVudDQwNjQ1MTc4NQ== | shoyer 1217238 | 2018-07-20T00:17:31Z | 2018-07-20T00:17:31Z | MEMBER | Hi @ctw, thanks for raising this issue. I think we'll be able to fix this eventually, but not until the large refactor envisioned by https://github.com/pydata/xarray/issues/1603. With the current version of xarray's data model this is basically unavoidable, because pandas.MultiIndex objects hold strings in dtype=object arrays. |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
string coords are converted to object dtype when using MultiIndex / stacking 340316108 |
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 3