-
-
Notifications
You must be signed in to change notification settings - Fork 757
Dask worker CLI error message might be misleading #9094
Copy link
Copy link
Open
Labels
enhancementImprove existing functionality or make things work betterImprove existing functionality or make things work bettergood first issueClearly described and easy to accomplish. Good for beginners to the project.Clearly described and easy to accomplish. Good for beginners to the project.p3Affects a small number of users or is largely cosmeticAffects a small number of users or is largely cosmetic
Description
Metadata
Metadata
Assignees
Labels
enhancementImprove existing functionality or make things work betterImprove existing functionality or make things work bettergood first issueClearly described and easy to accomplish. Good for beginners to the project.Clearly described and easy to accomplish. Good for beginners to the project.p3Affects a small number of users or is largely cosmeticAffects a small number of users or is largely cosmetic
Describe the issue:
Dask worker cli error message is not always helpful as it doesn't check for unknown options. It might be hard to understand what is wrong. (See discussion in https://dask.discourse.group/t/unexpected-dask-argument/3979).
Minimal Complete Verifiable Example:
outputs:
Which is true:
1is an argument, but in this case, a user wants to know that--nprocsis not a valid option.Anything else we need to know?:
This is probably due to the need to have a
preloadfree argv in thedask workercommand. So options are not enforced in click.I'd be happy to help, but I'm not a click expert and I'm not sure of the side effects of enabling options checking.