issue_comments
2 rows where author_association = "MEMBER", issue = 517195073 and user = 2448579 sorted by updated_at descending
This data as json, CSV (advanced)
Suggested facets: created_at (date), updated_at (date)
issue 1
- assign_coords with mixed DataArray / array args removes coords · 2 ✖
| id | html_url | issue_url | node_id | user | created_at | updated_at ▲ | author_association | body | reactions | performed_via_github_app | issue |
|---|---|---|---|---|---|---|---|---|---|---|---|
| 549456096 | https://github.com/pydata/xarray/issues/3483#issuecomment-549456096 | https://api.github.com/repos/pydata/xarray/issues/3483 | MDEyOklzc3VlQ29tbWVudDU0OTQ1NjA5Ng== | dcherian 2448579 | 2019-11-04T17:15:44Z | 2019-11-04T17:15:44Z | MEMBER | That is a good point. Let's see what @shoyer thinks. |
{
"total_count": 0,
"+1": 0,
"-1": 0,
"laugh": 0,
"hooray": 0,
"confused": 0,
"heart": 0,
"rocket": 0,
"eyes": 0
} |
assign_coords with mixed DataArray / array args removes coords 517195073 | |
| 549429956 | https://github.com/pydata/xarray/issues/3483#issuecomment-549429956 | https://api.github.com/repos/pydata/xarray/issues/3483 | MDEyOklzc3VlQ29tbWVudDU0OTQyOTk1Ng== | dcherian 2448579 | 2019-11-04T16:19:37Z | 2019-11-04T16:19:37Z | MEMBER | The The last example raises a |
{
"total_count": 0,
"+1": 0,
"-1": 0,
"laugh": 0,
"hooray": 0,
"confused": 0,
"heart": 0,
"rocket": 0,
"eyes": 0
} |
assign_coords with mixed DataArray / array args removes coords 517195073 |
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