Ensure HighLevelGraph
layers are Layer
instances
#5271
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.
This PR updates how we construct the
HighLevelGraph
insubset_dataset_to_block
. Currently we create aHighLevelGraph
and then manually add a few new layers, which aredict
s, directly tohlg.layers
.xarray/xarray/core/parallel.py
Lines 537 to 546 in eec2b59
However since (in more recent versions of Dask)
HighLevelGraph
layers are expected to beLayer
class instances this can result in unexpected errors (xref #5077 (comment)). Instead of manually adding new layers tohlg.layers
, this PR proposes we create a newHighLevelGraph
altogether to ensure thathlg.layers
won't contain any rawdict
layers.