conda environment completions never load: generator runs 'conva env list' (typo)

[vikvang]

Description

The get_conda_environments generator in command-signatures/src/generators/conda.rs runs conva env list — note the typo — so the command always fails and conda environment completions never appear.

Where

command-signatures/src/generators/conda.rs, get_conda_environments:

Generator::script(CommandBuilder::single_command("conva env list"), |output| {

Expected

The generator should run conda env list.

Impact

Environment-name completions for conda are silently broken — the generator produces no suggestions.

[warp-factories]

Here's what I found while triaging this issue:

Confirmed on main: get_conda_environments in command-signatures/src/generators/conda.rs (lines 18–28) runs CommandBuilder::single_command("conva env list") — a typo for conda. The other two generators in that file correctly use conda list and conda config --show, and conva appears nowhere else in the tree.

This generator is wired up from command-signatures/json/conda.json for conda activate (line 9) and conda create --clone (line 317). Generator::script only feeds the command's stdout into its parsing callback, so a failing conva invocation yields no output and therefore no suggestions — which matches the silent breakage you describe.

The fix is a one-character change on line 20: conva → conda. No other files need to change.

Related but separate: #382 covers parsing in get_installed_packages, not this typo.

Routing to @captainsafia to review and apply a gate label (ready-to-spec / ready-to-implement) if this should proceed.

This is my automated analysis and may be incorrect. A maintainer will verify the details.

Responding as Warp for OSS: Open session · View run

[warp-factories]

This issue has been marked ready for a specification. Community contributions are welcome — feel free to pick it up. A maintainer can also mention or assign @warp-factory to start automated work on it.

Responding as Warp for OSS: Open session · View run