issue_comments
2 rows where issue = 228872889 sorted by updated_at descending
This data as json, CSV (advanced)
Suggested facets: created_at (date), updated_at (date)
issue 1
- to_netcdf without path argument returns None rather than bytes · 2 ✖
| id | html_url | issue_url | node_id | user | created_at | updated_at ▲ | author_association | body | reactions | performed_via_github_app | issue |
|---|---|---|---|---|---|---|---|---|---|---|---|
| 302155985 | https://github.com/pydata/xarray/issues/1410#issuecomment-302155985 | https://api.github.com/repos/pydata/xarray/issues/1410 | MDEyOklzc3VlQ29tbWVudDMwMjE1NTk4NQ== | shoyer 1217238 | 2017-05-17T17:05:31Z | 2017-05-17T17:05:31Z | MEMBER | Yes, this is definitely a bug. |
{
"total_count": 0,
"+1": 0,
"-1": 0,
"laugh": 0,
"hooray": 0,
"confused": 0,
"heart": 0,
"rocket": 0,
"eyes": 0
} |
to_netcdf without path argument returns None rather than bytes 228872889 | |
| 301696656 | https://github.com/pydata/xarray/issues/1410#issuecomment-301696656 | https://api.github.com/repos/pydata/xarray/issues/1410 | MDEyOklzc3VlQ29tbWVudDMwMTY5NjY1Ng== | fmaussion 10050469 | 2017-05-16T07:16:47Z | 2017-05-16T07:16:47Z | MEMBER | Note that this works with a Dataset:
I see no reason why this shouldn't work with DataArrays, so I guess this is a bug. |
{
"total_count": 0,
"+1": 0,
"-1": 0,
"laugh": 0,
"hooray": 0,
"confused": 0,
"heart": 0,
"rocket": 0,
"eyes": 0
} |
to_netcdf without path argument returns None rather than bytes 228872889 |
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