issue_comments
4 rows where author_association = "CONTRIBUTOR" and issue = 253476466 sorted by updated_at descending
This data as json, CSV (advanced)
Suggested facets: created_at (date), updated_at (date)
issue 1
- Better compression algorithms for NetCDF · 4 ✖
id | html_url | issue_url | node_id | user | created_at | updated_at ▲ | author_association | body | reactions | performed_via_github_app | issue |
---|---|---|---|---|---|---|---|---|---|---|---|
325713273 | https://github.com/pydata/xarray/issues/1536#issuecomment-325713273 | https://api.github.com/repos/pydata/xarray/issues/1536 | MDEyOklzc3VlQ29tbWVudDMyNTcxMzI3Mw== | dopplershift 221526 | 2017-08-29T16:07:37Z | 2017-08-29T16:07:37Z | CONTRIBUTOR | Cool. Thx @shoyer . |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
Better compression algorithms for NetCDF 253476466 | |
325535079 | https://github.com/pydata/xarray/issues/1536#issuecomment-325535079 | https://api.github.com/repos/pydata/xarray/issues/1536 | MDEyOklzc3VlQ29tbWVudDMyNTUzNTA3OQ== | dopplershift 221526 | 2017-08-29T02:17:02Z | 2017-08-29T02:17:02Z | CONTRIBUTOR | (cc @WardF) Please, please, please don't write out "netCDF" files that don't conform to the spec. Either work with us to try to add the needed features to the spec (and the C-library) or call them something else. The spec exists for a reason. When such non-conformant files are distributed (and they will be), this creates a needless support load for the netcdf-c and netcdf-java developers (not to mention netCDF4-python).
You're not actually saying the netCDF-c library should check for this custom format, are you? |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
Better compression algorithms for NetCDF 253476466 | |
325515228 | https://github.com/pydata/xarray/issues/1536#issuecomment-325515228 | https://api.github.com/repos/pydata/xarray/issues/1536 | MDEyOklzc3VlQ29tbWVudDMyNTUxNTIyOA== | dopplershift 221526 | 2017-08-28T23:57:02Z | 2017-08-28T23:57:21Z | CONTRIBUTOR | But these are still considered netCDF files, not HDF5 files? As in, they declare attributes that say "this is a netCDF file"? |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
Better compression algorithms for NetCDF 253476466 | |
325513941 | https://github.com/pydata/xarray/issues/1536#issuecomment-325513941 | https://api.github.com/repos/pydata/xarray/issues/1536 | MDEyOklzc3VlQ29tbWVudDMyNTUxMzk0MQ== | dopplershift 221526 | 2017-08-28T23:48:10Z | 2017-08-28T23:48:10Z | CONTRIBUTOR | @shoyer I just want to clarify: is the netCDF C library able to read files using these features? |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
Better compression algorithms for NetCDF 253476466 |
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