issue_comments
5 rows where issue = 525903846 and user = 4179064 sorted by updated_at descending
This data as json, CSV (advanced)
Suggested facets: reactions, created_at (date), updated_at (date)
issue 1
- Dataset.drop() no longer works with a set as an argument · 5 ✖
id | html_url | issue_url | node_id | user | created_at | updated_at ▲ | author_association | body | reactions | performed_via_github_app | issue |
---|---|---|---|---|---|---|---|---|---|---|---|
556111055 | https://github.com/pydata/xarray/issues/3552#issuecomment-556111055 | https://api.github.com/repos/pydata/xarray/issues/3552 | MDEyOklzc3VlQ29tbWVudDU1NjExMTA1NQ== | xylar 4179064 | 2019-11-20T17:05:33Z | 2019-11-20T17:05:33Z | NONE | Ah, thanks very much! I'll switch to using that syntax instead. |
{ "total_count": 2, "+1": 2, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
Dataset.drop() no longer works with a set as an argument 525903846 | |
556096924 | https://github.com/pydata/xarray/issues/3552#issuecomment-556096924 | https://api.github.com/repos/pydata/xarray/issues/3552 | MDEyOklzc3VlQ29tbWVudDU1NjA5NjkyNA== | xylar 4179064 | 2019-11-20T16:53:40Z | 2019-11-20T16:53:40Z | NONE | I apologize for this slight tangent but it's related to why we use sets in |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
Dataset.drop() no longer works with a set as an argument 525903846 | |
556095452 | https://github.com/pydata/xarray/issues/3552#issuecomment-556095452 | https://api.github.com/repos/pydata/xarray/issues/3552 | MDEyOklzc3VlQ29tbWVudDU1NjA5NTQ1Mg== | xylar 4179064 | 2019-11-20T16:50:15Z | 2019-11-20T16:50:15Z | NONE |
Yes, I noticed that, too. I assumed it wasn't being documented anymore because it was considered deprecated. |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
Dataset.drop() no longer works with a set as an argument 525903846 | |
556091171 | https://github.com/pydata/xarray/issues/3552#issuecomment-556091171 | https://api.github.com/repos/pydata/xarray/issues/3552 | MDEyOklzc3VlQ29tbWVudDU1NjA5MTE3MQ== | xylar 4179064 | 2019-11-20T16:41:09Z | 2019-11-20T16:43:01Z | NONE |
I'm confused. In 0.14.1,
Yes, I switched to So @rabernat and @dcherian, please clarify if I should be switching to |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
Dataset.drop() no longer works with a set as an argument 525903846 | |
556077504 | https://github.com/pydata/xarray/issues/3552#issuecomment-556077504 | https://api.github.com/repos/pydata/xarray/issues/3552 | MDEyOklzc3VlQ29tbWVudDU1NjA3NzUwNA== | xylar 4179064 | 2019-11-20T16:10:54Z | 2019-11-20T16:11:13Z | NONE | I believe a |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
Dataset.drop() no longer works with a set as an argument 525903846 |
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