issue_comments
2 rows where issue = 392362056 sorted by updated_at descending
This data as json, CSV (advanced)
Suggested facets: created_at (date), updated_at (date)
issue 1
- Selection of MultiIndex makes following `unstack` wrong · 2 ✖
| id | html_url | issue_url | node_id | user | created_at | updated_at ▲ | author_association | body | reactions | performed_via_github_app | issue |
|---|---|---|---|---|---|---|---|---|---|---|---|
| 448536594 | https://github.com/pydata/xarray/issues/2619#issuecomment-448536594 | https://api.github.com/repos/pydata/xarray/issues/2619 | MDEyOklzc3VlQ29tbWVudDQ0ODUzNjU5NA== | fujiisoup 6815844 | 2018-12-19T09:56:45Z | 2018-12-19T09:56:45Z | MEMBER | Thanks @shoyer I also noticed that the |
{
"total_count": 0,
"+1": 0,
"-1": 0,
"laugh": 0,
"hooray": 0,
"confused": 0,
"heart": 0,
"rocket": 0,
"eyes": 0
} |
Selection of MultiIndex makes following `unstack` wrong 392362056 | |
| 448474051 | https://github.com/pydata/xarray/issues/2619#issuecomment-448474051 | https://api.github.com/repos/pydata/xarray/issues/2619 | MDEyOklzc3VlQ29tbWVudDQ0ODQ3NDA1MQ== | shoyer 1217238 | 2018-12-19T05:27:53Z | 2018-12-19T05:27:53Z | MEMBER | I agree, this is an xarray bug. It seems that we need to drop unused levels in the MultiIndex as part of |
{
"total_count": 0,
"+1": 0,
"-1": 0,
"laugh": 0,
"hooray": 0,
"confused": 0,
"heart": 0,
"rocket": 0,
"eyes": 0
} |
Selection of MultiIndex makes following `unstack` wrong 392362056 |
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 2