fix: protect Uproot's 'project_columns' from Dask node names. #801
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.
When computing Dask graphs with a operations inside a
__getitem__
,Uproot is receiving names like "less-06b0b18209c65504e8506df9da02f75d" as branch names in
project_columns
. The strings we get inproject_columns
should be a strict subset of the strings in the input set of columns. This PR selects that subset, but it shouldn't be happening on the dask-awkward end.I'm using a version of dask-awkward from git...
7fe448a1d448fa30f09693be0b14634c7968161a
from December 9, 2022.