issue_comments
2 rows where author_association = "MEMBER", issue = 261403591 and user = 2443309 sorted by updated_at descending
This data as json, CSV (advanced)
issue 1
- Need better user control of _FillValue attribute in NetCDF files · 2 ✖
id | html_url | issue_url | node_id | user | created_at | updated_at ▲ | author_association | body | reactions | performed_via_github_app | issue |
---|---|---|---|---|---|---|---|---|---|---|---|
333171129 | https://github.com/pydata/xarray/issues/1598#issuecomment-333171129 | https://api.github.com/repos/pydata/xarray/issues/1598 | MDEyOklzc3VlQ29tbWVudDMzMzE3MTEyOQ== | jhamman 2443309 | 2017-09-29T16:17:32Z | 2017-09-29T16:17:32Z | MEMBER | @dnowacki-usgs - you've made a good point. At least for the netCDF4 backend, this seems to work out of the box with None/False. Can someone check that this works for the scipy/h5netcdf backends? |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
Need better user control of _FillValue attribute in NetCDF files 261403591 | |
332950001 | https://github.com/pydata/xarray/issues/1598#issuecomment-332950001 | https://api.github.com/repos/pydata/xarray/issues/1598 | MDEyOklzc3VlQ29tbWVudDMzMjk1MDAwMQ== | jhamman 2443309 | 2017-09-28T20:10:13Z | 2017-09-28T20:10:13Z | MEMBER | I actually think we should use |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
Need better user control of _FillValue attribute in NetCDF files 261403591 |
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