html_url,issue_url,id,node_id,user,created_at,updated_at,author_association,body,reactions,performed_via_github_app,issue
https://github.com/pydata/xarray/issues/2503#issuecomment-432796835,https://api.github.com/repos/pydata/xarray/issues/2503,432796835,MDEyOklzc3VlQ29tbWVudDQzMjc5NjgzNQ==,950575,2018-10-24T19:29:11Z,2018-10-24T19:29:11Z,CONTRIBUTOR,"> h10edf3e_1 contains the timeout fix and is build against hdf5 1.10.2. The `conda-forge` h9cd6fdc_11 build is against hdf5 1.10.3 perhaps that makes a different?

There are many variables at play here. The env that solved it in https://github.com/pydata/xarray/issues/2503#issuecomment-432645477 seems quite different from the env where the problem happened, including an `xarray` dev version. I'm not sure `hdf5` is a good candidate to blame :smile:","{""total_count"": 0, ""+1"": 0, ""-1"": 0, ""laugh"": 0, ""hooray"": 0, ""confused"": 0, ""heart"": 0, ""rocket"": 0, ""eyes"": 0}",,373121666
https://github.com/pydata/xarray/issues/2503#issuecomment-432788686,https://api.github.com/repos/pydata/xarray/issues/2503,432788686,MDEyOklzc3VlQ29tbWVudDQzMjc4ODY4Ng==,1050278,2018-10-24T19:04:44Z,2018-10-24T19:04:44Z,CONTRIBUTOR,h10edf3e_1 contains the timeout fix and is build against hdf5 1.10.2. The `conda-forge` h9cd6fdc_11 build is against hdf5 1.10.3 perhaps that makes a different?,"{""total_count"": 0, ""+1"": 0, ""-1"": 0, ""laugh"": 0, ""hooray"": 0, ""confused"": 0, ""heart"": 0, ""rocket"": 0, ""eyes"": 0}",,373121666
https://github.com/pydata/xarray/issues/2503#issuecomment-432784219,https://api.github.com/repos/pydata/xarray/issues/2503,432784219,MDEyOklzc3VlQ29tbWVudDQzMjc4NDIxOQ==,950575,2018-10-24T18:53:22Z,2018-10-24T18:53:22Z,CONTRIBUTOR,"> In `defaults` libnetcdf4 4.6.1 build 1 and above contain the timeout fix, build 0 has the original timeout.

Thanks @jjhelmus! I guess that info and https://github.com/pydata/xarray/issues/2503#issuecomment-432483817 eliminates the timeout issue from the equation.","{""total_count"": 0, ""+1"": 0, ""-1"": 0, ""laugh"": 0, ""hooray"": 0, ""confused"": 0, ""heart"": 0, ""rocket"": 0, ""eyes"": 0}",,373121666
https://github.com/pydata/xarray/issues/2503#issuecomment-432783232,https://api.github.com/repos/pydata/xarray/issues/2503,432783232,MDEyOklzc3VlQ29tbWVudDQzMjc4MzIzMg==,1050278,2018-10-24T18:50:48Z,2018-10-24T18:50:48Z,CONTRIBUTOR,"In `defaults` libnetcdf4 4.6.1 build 1 and above contain the timeout fix, build 0 has the original timeout.","{""total_count"": 0, ""+1"": 0, ""-1"": 0, ""laugh"": 0, ""hooray"": 0, ""confused"": 0, ""heart"": 0, ""rocket"": 0, ""eyes"": 0}",,373121666
https://github.com/pydata/xarray/issues/2503#issuecomment-432747410,https://api.github.com/repos/pydata/xarray/issues/2503,432747410,MDEyOklzc3VlQ29tbWVudDQzMjc0NzQxMA==,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}",,373121666
https://github.com/pydata/xarray/issues/2503#issuecomment-432746421,https://api.github.com/repos/pydata/xarray/issues/2503,432746421,MDEyOklzc3VlQ29tbWVudDQzMjc0NjQyMQ==,950575,2018-10-24T17:10:44Z,2018-10-24T17:10:44Z,CONTRIBUTOR,"> That version has the fix for the issue.

I know that @jjhelmus ported the fix to `defaults` but I'm not sure which build number has it, and/or if the previous one was remove, b/c defaults builds are not as transparent as `conda-forge`'s :smile:

He can probably say more about that.","{""total_count"": 0, ""+1"": 0, ""-1"": 0, ""laugh"": 0, ""hooray"": 0, ""confused"": 0, ""heart"": 0, ""rocket"": 0, ""eyes"": 0}",,373121666
https://github.com/pydata/xarray/issues/2503#issuecomment-432744441,https://api.github.com/repos/pydata/xarray/issues/2503,432744441,MDEyOklzc3VlQ29tbWVudDQzMjc0NDQ0MQ==,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}",,373121666
https://github.com/pydata/xarray/issues/2503#issuecomment-432739449,https://api.github.com/repos/pydata/xarray/issues/2503,432739449,MDEyOklzc3VlQ29tbWVudDQzMjczOTQ0OQ==,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}",,373121666
https://github.com/pydata/xarray/issues/2503#issuecomment-432422763,https://api.github.com/repos/pydata/xarray/issues/2503,432422763,MDEyOklzc3VlQ29tbWVudDQzMjQyMjc2Mw==,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}",,373121666
https://github.com/pydata/xarray/issues/2503#issuecomment-432370887,https://api.github.com/repos/pydata/xarray/issues/2503,432370887,MDEyOklzc3VlQ29tbWVudDQzMjM3MDg4Nw==,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}",,373121666