issue_comments
2 rows where issue = 188985482 and user = 1217238 sorted by updated_at descending
This data as json, CSV (advanced)
Suggested facets: created_at (date), updated_at (date)
issue 1
- Converting rasm file to netCDF3 using xarray · 2 ✖
| id | html_url | issue_url | node_id | user | created_at | updated_at ▲ | author_association | body | reactions | performed_via_github_app | issue |
|---|---|---|---|---|---|---|---|---|---|---|---|
| 269389355 | https://github.com/pydata/xarray/issues/1114#issuecomment-269389355 | https://api.github.com/repos/pydata/xarray/issues/1114 | MDEyOklzc3VlQ29tbWVudDI2OTM4OTM1NQ== | shoyer 1217238 | 2016-12-27T22:06:35Z | 2016-12-27T22:06:35Z | MEMBER | It looks like scipy gets confused between the the The simple work around is to remove the |
{
"total_count": 0,
"+1": 0,
"-1": 0,
"laugh": 0,
"hooray": 0,
"confused": 0,
"heart": 0,
"rocket": 0,
"eyes": 0
} |
Converting rasm file to netCDF3 using xarray 188985482 | |
| 260203017 | https://github.com/pydata/xarray/issues/1114#issuecomment-260203017 | https://api.github.com/repos/pydata/xarray/issues/1114 | MDEyOklzc3VlQ29tbWVudDI2MDIwMzAxNw== | shoyer 1217238 | 2016-11-13T18:31:48Z | 2016-11-13T18:31:48Z | MEMBER | Can you write it as netcdf3 using engine="netcdf4"? This might be a scipy bug. |
{
"total_count": 0,
"+1": 0,
"-1": 0,
"laugh": 0,
"hooray": 0,
"confused": 0,
"heart": 0,
"rocket": 0,
"eyes": 0
} |
Converting rasm file to netCDF3 using xarray 188985482 |
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