Turning on single-threaded handling in dask #457
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
This PR is to fix segfaults in testing and docs building when
xarray.open_mfdataset
is used. This is due to underlying issues with the netCDF code not being thread safe. We previously turned onlock=False
in that command, following advice here:pydata/xarray#3961
And that worked, but the issue has started occurring again. Following the advice in this issue thread:
pydata/xarray#7079
this PR now explicitly sets the
dask
scheduler to use single-threading.Fixes #354
Type of change
Key checklist
pre-commit
checks:$ pre-commit run -a
$ poetry run pytest
Further checks