issue_comments
9 rows where issue = 396285440 sorted by updated_at descending
This data as json, CSV (advanced)
Suggested facets: created_at (date), updated_at (date)
issue 1
- dataset info in .json format · 9 ✖
id | html_url | issue_url | node_id | user | created_at | updated_at ▲ | author_association | body | reactions | performed_via_github_app | issue |
---|---|---|---|---|---|---|---|---|---|---|---|
572293244 | https://github.com/pydata/xarray/issues/2656#issuecomment-572293244 | https://api.github.com/repos/pydata/xarray/issues/2656 | MDEyOklzc3VlQ29tbWVudDU3MjI5MzI0NA== | rafa-guedes 7799184 | 2020-01-08T22:42:01Z | 2020-01-08T22:43:25Z | CONTRIBUTOR | Pandas has an option |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
dataset info in .json format 396285440 | |
572146221 | https://github.com/pydata/xarray/issues/2656#issuecomment-572146221 | https://api.github.com/repos/pydata/xarray/issues/2656 | MDEyOklzc3VlQ29tbWVudDU3MjE0NjIyMQ== | shoyer 1217238 | 2020-01-08T16:23:35Z | 2020-01-08T16:23:35Z | MEMBER |
What's the right way to serialize datetime objects in JSON? One option would be to add an |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
dataset info in .json format 396285440 | |
572054942 | https://github.com/pydata/xarray/issues/2656#issuecomment-572054942 | https://api.github.com/repos/pydata/xarray/issues/2656 | MDEyOklzc3VlQ29tbWVudDU3MjA1NDk0Mg== | rafa-guedes 7799184 | 2020-01-08T13:36:41Z | 2020-01-08T13:36:41Z | CONTRIBUTOR | Would it make sense having |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
dataset info in .json format 396285440 | |
462912011 | https://github.com/pydata/xarray/issues/2656#issuecomment-462912011 | https://api.github.com/repos/pydata/xarray/issues/2656 | MDEyOklzc3VlQ29tbWVudDQ2MjkxMjAxMQ== | jhamman 2443309 | 2019-02-12T20:01:07Z | 2019-02-12T20:01:07Z | MEMBER | It would be good to figure out if either of these are used. It's not too late to update your implementation. |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
dataset info in .json format 396285440 | |
462902513 | https://github.com/pydata/xarray/issues/2656#issuecomment-462902513 | https://api.github.com/repos/pydata/xarray/issues/2656 | MDEyOklzc3VlQ29tbWVudDQ2MjkwMjUxMw== | rabernat 1197350 | 2019-02-12T19:35:08Z | 2019-02-12T19:35:08Z | MEMBER | Since my PR was merged, I have discovered two different JSON representations of netcdf - https://binary-array-ld.github.io/netcdf-ld/ - http://cf-json.org/specification Oops! |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
dataset info in .json format 396285440 | |
454179986 | https://github.com/pydata/xarray/issues/2656#issuecomment-454179986 | https://api.github.com/repos/pydata/xarray/issues/2656 | MDEyOklzc3VlQ29tbWVudDQ1NDE3OTk4Ng== | dopplershift 221526 | 2019-01-14T22:07:19Z | 2019-01-14T22:07:19Z | CONTRIBUTOR | I'm not aware of any standard out there for JSON representation of netCDF, but I know it's been at least (briefly) discussed. @WardF, anything out there you're aware of? Another spelling of this could be |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
dataset info in .json format 396285440 | |
451777071 | https://github.com/pydata/xarray/issues/2656#issuecomment-451777071 | https://api.github.com/repos/pydata/xarray/issues/2656 | MDEyOklzc3VlQ29tbWVudDQ1MTc3NzA3MQ== | jhamman 2443309 | 2019-01-06T21:35:50Z | 2019-01-06T21:35:50Z | MEMBER | Just to say, I really like this idea. I think I prefer the |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
dataset info in .json format 396285440 | |
451771761 | https://github.com/pydata/xarray/issues/2656#issuecomment-451771761 | https://api.github.com/repos/pydata/xarray/issues/2656 | MDEyOklzc3VlQ29tbWVudDQ1MTc3MTc2MQ== | rabernat 1197350 | 2019-01-06T20:24:48Z | 2019-01-06T20:24:48Z | MEMBER | I will ping @dopplershift of Unidata, my go-to for all things netCDF. 😉 Ryan, do you know of any work on this area? The best I could google is this thread from the netcdf mailing list. |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
dataset info in .json format 396285440 | |
451771539 | https://github.com/pydata/xarray/issues/2656#issuecomment-451771539 | https://api.github.com/repos/pydata/xarray/issues/2656 | MDEyOklzc3VlQ29tbWVudDQ1MTc3MTUzOQ== | shoyer 1217238 | 2019-01-06T20:21:23Z | 2019-01-06T20:21:23Z | MEMBER | I like the look of
|
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
dataset info in .json format 396285440 |
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 5