Skip to content

Conversation

@TomAugspurger
Copy link
Contributor

Newer versions of Dask don't like a mixture of dask and non-dask objects in client.compute(). Previously, calculate_parts_to_sizes() passed a list[tuple[str, Future]] to client.compute(). This updates it to only pass through the Futures.

Newer versions of Dask don't like a mixture of dask and non-dask objects
in `client.compute()`. Previously, `calculate_parts_to_sizes()` passed
a list[tuple[str, Future]] to `client.compute()`. This updates it to
only pass through the Futures.
@TomAugspurger TomAugspurger requested a review from a team as a code owner May 15, 2025 16:33
@github-actions github-actions bot added the Cython / Python Cython or Python issue label May 15, 2025
@jcrist jcrist added improvement Improvement / enhancement to an existing function non-breaking Non-breaking change labels May 15, 2025
@TomAugspurger
Copy link
Contributor Author

The previous failure is hopefully fixed by a change in dask / rapids-dask-dependency. Pushed an empty commit to retrigger CI now that that's in.

@csadorf
Copy link
Contributor

csadorf commented May 15, 2025

/merge

@rapids-bot rapids-bot bot merged commit 56c6920 into rapidsai:branch-25.06 May 15, 2025
89 checks passed
@TomAugspurger TomAugspurger deleted the tom/dask-compat-ucxx branch May 15, 2025 20:51
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Cython / Python Cython or Python issue improvement Improvement / enhancement to an existing function non-breaking Non-breaking change

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants