issue_comments
5 rows where issue = 476494705 and user = 868027 sorted by updated_at descending
This data as json, CSV (advanced)
Suggested facets: created_at (date), updated_at (date)
issue 1
- RTD build failing · 5 ✖
id | html_url | issue_url | node_id | user | created_at | updated_at ▲ | author_association | body | reactions | performed_via_github_app | issue |
---|---|---|---|---|---|---|---|---|---|---|---|
518677703 | https://github.com/pydata/xarray/issues/3182#issuecomment-518677703 | https://api.github.com/repos/pydata/xarray/issues/3182 | MDEyOklzc3VlQ29tbWVudDUxODY3NzcwMw== | DocOtak 868027 | 2019-08-06T13:49:47Z | 2019-08-06T13:49:47Z | CONTRIBUTOR | Seems the docs are still failing to build, except this time it is being killed due to too much resource consumption. |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
RTD build failing 476494705 | |
518426134 | https://github.com/pydata/xarray/issues/3182#issuecomment-518426134 | https://api.github.com/repos/pydata/xarray/issues/3182 | MDEyOklzc3VlQ29tbWVudDUxODQyNjEzNA== | DocOtak 868027 | 2019-08-05T22:32:12Z | 2019-08-05T22:32:12Z | CONTRIBUTOR | @max-sixty I made a PR which bumps rasterio. Something else to consider is enabling channel_priority strict in the conda environment. When I had enabled that in local testing, the conda solver was unable to create the requested environment. It seemed the requested rasterio version was no longer on conda-forge (though maybe under the cf201901 label?). Though if I recall, there was also a mismatch between the requested pandas and python versions when strict was enabled. It seems the trade off is where you want the failure to occur, either in making the environment in conda, or when some package stops working. |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
RTD build failing 476494705 | |
518381266 | https://github.com/pydata/xarray/issues/3182#issuecomment-518381266 | https://api.github.com/repos/pydata/xarray/issues/3182 | MDEyOklzc3VlQ29tbWVudDUxODM4MTI2Ng== | DocOtak 868027 | 2019-08-05T20:12:37Z | 2019-08-05T20:12:37Z | CONTRIBUTOR | So it looks more like a conda channel mixing problem to me now. Perhaps just bumping rasterio to 1.0.24? |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
RTD build failing 476494705 | |
518368420 | https://github.com/pydata/xarray/issues/3182#issuecomment-518368420 | https://api.github.com/repos/pydata/xarray/issues/3182 | MDEyOklzc3VlQ29tbWVudDUxODM2ODQyMA== | DocOtak 868027 | 2019-08-05T19:32:10Z | 2019-08-05T19:32:10Z | CONTRIBUTOR | Has anyone with access tried just wiping the env? https://docs.readthedocs.io/en/stable/guides/wipe-environment.html Specifically, when I was testing locally my rasterio was not importing, but at some point in the past, had run successfully. I was able to fix by removing the |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
RTD build failing 476494705 | |
518062884 | https://github.com/pydata/xarray/issues/3182#issuecomment-518062884 | https://api.github.com/repos/pydata/xarray/issues/3182 | MDEyOklzc3VlQ29tbWVudDUxODA2Mjg4NA== | DocOtak 868027 | 2019-08-05T02:25:02Z | 2019-08-05T02:25:02Z | CONTRIBUTOR | More information here: https://sphinx-gallery.github.io/configuration.html#don-t-fail-the-build-on-exit |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
RTD build failing 476494705 |
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