issue_comments
2 rows where issue = 412623833 sorted by updated_at descending
This data as json, CSV (advanced)
Suggested facets: created_at (date), updated_at (date)
issue 1
- enable reading of file-like HDF5 objects · 2 ✖
id | html_url | issue_url | node_id | user | created_at | updated_at ▲ | author_association | body | reactions | performed_via_github_app | issue |
---|---|---|---|---|---|---|---|---|---|---|---|
467689325 | https://github.com/pydata/xarray/issues/2781#issuecomment-467689325 | https://api.github.com/repos/pydata/xarray/issues/2781 | MDEyOklzc3VlQ29tbWVudDQ2NzY4OTMyNQ== | scottyhq 3924836 | 2019-02-27T01:44:45Z | 2019-02-27T01:44:45Z | MEMBER | Just noting here that I've gotten this to work reading a netcd4/fhdf5 file via gcsfs, but not for the same file accessed via s3fs: https://github.com/dask/s3fs/issues/168 |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
enable reading of file-like HDF5 objects 412623833 | |
466261250 | https://github.com/pydata/xarray/issues/2781#issuecomment-466261250 | https://api.github.com/repos/pydata/xarray/issues/2781 | MDEyOklzc3VlQ29tbWVudDQ2NjI2MTI1MA== | shoyer 1217238 | 2019-02-22T03:32:47Z | 2019-02-22T03:32:47Z | MEMBER | Yes, this would be a welcome feature addition! It looks like you've already gotten started -- let me know if you have any further questions. |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
enable reading of file-like HDF5 objects 412623833 |
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