Clean up deprecations in CLI#9240
Conversation
Unit Test ResultsSee test report for an extended history of previous test failures. This is useful for diagnosing flaky tests. 30 files ± 0 30 suites ±0 11h 1m 5s ⏱️ - 1m 52s For more details on these failures, see this check. Results for commit 0f70b55. ± Comparison against base commit d9c0010. This pull request removes 3 tests. |
| CLICK_VERSION = tuple(map(int, importlib.metadata.version("click").split(".")[:2])) | ||
|
|
||
|
|
||
| def install_signal_handlers(loop=None, cleanup=None): |
There was a problem hiding this comment.
This is currently used in Dask-CUDA. Was this API deprecated? cc @TomAugspurger @pentschev for viz
There was a problem hiding this comment.
Yeah. Dunno how we missed it :/
There was a problem hiding this comment.
Thanks for catching this, Rick. I think you're right, we should be more aligned with how Distributed is currently handling signals and thus rapidsai/dask-cuda#1651 looks like the proper solution.
There was a problem hiding this comment.
Is it acceptable to have this PR in the next distributed release, or do you prefer reverting it and doing it again in a few months?
There was a problem hiding this comment.
I'll let @TomAugspurger answer that definitively, but AFAIK the latest Dask release (2026.3.0) will be used for the upcoming RAPIDS 25.06 release and thus we do not need to make changes for this release. For the next RAPIDS release expected only for August, it should be ok for us to use the changes from rapidsai/dask-cuda#1651 that drop the use of install_signal_handlers unless we find out any issues with that within the next ~2 months.
The `install_signal_handlers` utility was unused in distributed, and was removed in dask/distributed#9240 This PR simply follows the pattern used in dask/distributed#6205 to migrate to `wait_for_signals`. Authors: - Richard (Rick) Zamora (https://github.com/rjzamora) Approvers: - Peter Andreas Entschev (https://github.com/pentschev) URL: #1651
No description provided.