issue_comments
5 rows where author_association = "NONE", issue = 646716560 and user = 15720911 sorted by updated_at descending
This data as json, CSV (advanced)
Suggested facets: created_at (date), updated_at (date)
issue 1
- to_xarray() result is incorrect when one of multi-index levels is not sorted · 5 ✖
id | html_url | issue_url | node_id | user | created_at | updated_at ▲ | author_association | body | reactions | performed_via_github_app | issue |
---|---|---|---|---|---|---|---|---|---|---|---|
652064154 | https://github.com/pydata/xarray/issues/4186#issuecomment-652064154 | https://api.github.com/repos/pydata/xarray/issues/4186 | MDEyOklzc3VlQ29tbWVudDY1MjA2NDE1NA== | Li9htmare 15720911 | 2020-06-30T21:48:33Z | 2020-06-30T21:48:33Z | NONE | This intention of variables used constructing the Dataset looks a lot clearer now. Many thanks Stephan! |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
to_xarray() result is incorrect when one of multi-index levels is not sorted 646716560 | |
651984472 | https://github.com/pydata/xarray/issues/4186#issuecomment-651984472 | https://api.github.com/repos/pydata/xarray/issues/4186 | MDEyOklzc3VlQ29tbWVudDY1MTk4NDQ3Mg== | Li9htmare 15720911 | 2020-06-30T19:02:28Z | 2020-06-30T19:02:28Z | NONE | Sorry @shoyer, I didn't notice you have pushed new commits to #4184 and thought you meant to just remove the |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
to_xarray() result is incorrect when one of multi-index levels is not sorted 646716560 | |
651674763 | https://github.com/pydata/xarray/issues/4186#issuecomment-651674763 | https://api.github.com/repos/pydata/xarray/issues/4186 | MDEyOklzc3VlQ29tbWVudDY1MTY3NDc2Mw== | Li9htmare 15720911 | 2020-06-30T09:24:13Z | 2020-06-30T09:24:13Z | NONE | Hi @shoyer , without I agree it will be better if we can maintain the order from |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
to_xarray() result is incorrect when one of multi-index levels is not sorted 646716560 | |
651424721 | https://github.com/pydata/xarray/issues/4186#issuecomment-651424721 | https://api.github.com/repos/pydata/xarray/issues/4186 | MDEyOklzc3VlQ29tbWVudDY1MTQyNDcyMQ== | Li9htmare 15720911 | 2020-06-29T23:40:41Z | 2020-06-29T23:41:45Z | NONE | Hi @shoyer, sorry I got you confused, I should have run your code at first place. You code removes the problematic Using pzhlobi's example Using the same |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
to_xarray() result is incorrect when one of multi-index levels is not sorted 646716560 | |
650738680 | https://github.com/pydata/xarray/issues/4186#issuecomment-650738680 | https://api.github.com/repos/pydata/xarray/issues/4186 | MDEyOklzc3VlQ29tbWVudDY1MDczODY4MA== | Li9htmare 15720911 | 2020-06-28T11:37:20Z | 2020-06-28T11:37:20Z | NONE | It seems the problem here is in Then in Besides the perf improvement it provides, #4184 seems also have a nice side effect fixing this issue. |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
to_xarray() result is incorrect when one of multi-index levels is not sorted 646716560 |
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