issue_comments
4 rows where issue = 191822204 sorted by updated_at descending
This data as json, CSV (advanced)
Suggested facets: created_at (date), updated_at (date)
issue 1
- Further attempt to get netCDF4 working on RTD · 4 ✖
id | html_url | issue_url | node_id | user | created_at | updated_at ▲ | author_association | body | reactions | performed_via_github_app | issue |
---|---|---|---|---|---|---|---|---|---|---|---|
263244991 | https://github.com/pydata/xarray/pull/1134#issuecomment-263244991 | https://api.github.com/repos/pydata/xarray/issues/1134 | MDEyOklzc3VlQ29tbWVudDI2MzI0NDk5MQ== | ocefpaf 950575 | 2016-11-28T11:11:24Z | 2016-11-28T11:11:24Z | CONTRIBUTOR | TL;DR you may consider making this change permanent. @fmaussion the problem is that latest conda-forge's hdf4 does ship with libmfhdf.so.0 but either defaults' version does not or an old version in conda-forge is broken. (I am traveling but I'll confirm that as soon as I get back.) Adding hdf4 at the env creation forces the solver to get the latest version/build number and prevented the downgrade in the subsequent conda install call. So you should probably leave hdf4 there even if it is over specifying deps because the issue may resurface. I say that b/c, if the bad version is in conda-forge we can remove it. But if it is in defaults we have no control. |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
Further attempt to get netCDF4 working on RTD 191822204 | |
263088421 | https://github.com/pydata/xarray/pull/1134#issuecomment-263088421 | https://api.github.com/repos/pydata/xarray/issues/1134 | MDEyOklzc3VlQ29tbWVudDI2MzA4ODQyMQ== | fmaussion 10050469 | 2016-11-26T21:59:21Z | 2016-11-26T21:59:21Z | MEMBER | Note that probably some other package than hdf4 might do it, as long as it ships that CC @ocefpaf |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
Further attempt to get netCDF4 working on RTD 191822204 | |
263088325 | https://github.com/pydata/xarray/pull/1134#issuecomment-263088325 | https://api.github.com/repos/pydata/xarray/issues/1134 | MDEyOklzc3VlQ29tbWVudDI2MzA4ODMyNQ== | fmaussion 10050469 | 2016-11-26T21:57:26Z | 2016-11-26T21:57:26Z | MEMBER | Yep, that did the trick: http://xarray.pydata.org/en/latest/examples/multidimensional-coords.html |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
Further attempt to get netCDF4 working on RTD 191822204 | |
263087945 | https://github.com/pydata/xarray/pull/1134#issuecomment-263087945 | https://api.github.com/repos/pydata/xarray/issues/1134 | MDEyOklzc3VlQ29tbWVudDI2MzA4Nzk0NQ== | shoyer 1217238 | 2016-11-26T21:48:50Z | 2016-11-26T21:48:50Z | MEMBER | Okay, let's try it. |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
Further attempt to get netCDF4 working on RTD 191822204 |
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 3