issue_comments
5 rows where issue = 373121666 and user = 221526 sorted by updated_at descending
This data as json, CSV (advanced)
Suggested facets: reactions, created_at (date), updated_at (date)
issue 1
- Problems with distributed and opendap netCDF endpoint · 5 ✖
id | html_url | issue_url | node_id | user | created_at | updated_at ▲ | author_association | body | reactions | performed_via_github_app | issue |
---|---|---|---|---|---|---|---|---|---|---|---|
432747410 | https://github.com/pydata/xarray/issues/2503#issuecomment-432747410 | https://api.github.com/repos/pydata/xarray/issues/2503 | MDEyOklzc3VlQ29tbWVudDQzMjc0NzQxMA== | dopplershift 221526 | 2018-10-24T17:13:14Z | 2018-10-24T17:13:14Z | CONTRIBUTOR | Oh, I didn't even catch that the original was on defaults. |
{ "total_count": 1, "+1": 0, "-1": 0, "laugh": 1, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
Problems with distributed and opendap netCDF endpoint 373121666 | |
432744441 | https://github.com/pydata/xarray/issues/2503#issuecomment-432744441 | https://api.github.com/repos/pydata/xarray/issues/2503 | MDEyOklzc3VlQ29tbWVudDQzMjc0NDQ0MQ== | dopplershift 221526 | 2018-10-24T17:06:01Z | 2018-10-24T17:06:01Z | CONTRIBUTOR | That version has the fix for the issue. |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
Problems with distributed and opendap netCDF endpoint 373121666 | |
432739449 | https://github.com/pydata/xarray/issues/2503#issuecomment-432739449 | https://api.github.com/repos/pydata/xarray/issues/2503 | MDEyOklzc3VlQ29tbWVudDQzMjczOTQ0OQ== | dopplershift 221526 | 2018-10-24T16:54:05Z | 2018-10-24T16:54:05Z | CONTRIBUTOR | The original version of libnetcdf in @rabernat 's environment definitely had the opendap timeout issue. Not sure if that's the root cause of the problem, or not, but it's suspect. |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
Problems with distributed and opendap netCDF endpoint 373121666 | |
432422763 | https://github.com/pydata/xarray/issues/2503#issuecomment-432422763 | https://api.github.com/repos/pydata/xarray/issues/2503 | MDEyOklzc3VlQ29tbWVudDQzMjQyMjc2Mw== | dopplershift 221526 | 2018-10-23T21:16:05Z | 2018-10-23T21:16:16Z | CONTRIBUTOR | @lesserwhirls That's an interesting idea. (@rsignell-usgs That's the one.) @rabernat What version of the conda-forge libnetcdf package is deployed wherever you're running? |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
Problems with distributed and opendap netCDF endpoint 373121666 | |
432370887 | https://github.com/pydata/xarray/issues/2503#issuecomment-432370887 | https://api.github.com/repos/pydata/xarray/issues/2503 | MDEyOklzc3VlQ29tbWVudDQzMjM3MDg4Nw== | dopplershift 221526 | 2018-10-23T18:43:23Z | 2018-10-23T18:43:23Z | CONTRIBUTOR | Just so I'm clear on how the workflow looks: 1. Open dataset with NetCDF/OPeNDAP 2. Serialize NetCDFDataStore (pickle? netcdf file?) 3. Ship to Dask workers 4. Reconstitute NetCDFDataStore Certainly does seem like there's something stale in what the remote workers are getting. Confused why it works for the others, though. I can prioritize this a bit and dig in to see what I can figure out--though I'm teaching through tomorrow. May be able to dig into this while at ECMWF. |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
Problems with distributed and opendap netCDF endpoint 373121666 |
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