Skip to content

docs: remove references to removed --no-verify-script launch flag - #3959

Open
latent-9 wants to merge 1 commit into
ml-explore:mainfrom
latent-9:fix-stale-no-verify-script-doc
Open

docs: remove references to removed --no-verify-script launch flag#3959
latent-9 wants to merge 1 commit into
ml-explore:mainfrom
latent-9:fix-stale-no-verify-script-doc

Conversation

@latent-9

Copy link
Copy Markdown

The distributed-launch guide documents a --no-verify-script flag for mlx.launch, but that flag was removed from the launcher.

python/mlx/_distributed_utils/launch.py (the mlx.launch entry point) defines no --no-verify-script option and contains no script-verification logic — grep for verify there returns nothing. The flag and its logic were removed in the launcher cleanup (PR #3513); this doc page was last edited before that and went stale.

Because launch.py uses parse_known_args(), the documented command does not error cleanly — --no-verify-script falls into the leftover args, and since it is not --, the launcher treats --no-verify-script as the program to run instead of ./my-job.sh, so the job does not run as documented.

This removes the flag from the example command and deletes the paragraph describing the no-longer-existent feature. Docs-only, no functional change.

The distributed launch guide documents a --no-verify-script flag for mlx.launch,
but that flag (and its script-verification logic) was removed from
python/mlx/_distributed_utils/launch.py. As written, the example command passes
--no-verify-script through parse_known_args and mlx.launch treats it as the
program to run instead of ./my-job.sh. Drop the flag from the example and remove
the paragraph describing the no-longer-existent feature.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant