`destroy` sans terminal répond « Aborted. » au lieu de réclamer `--yes` comme `clean` et `reset`
Maintainers usually reply within 1 day
A pull request for this has already been merged.
- #356 by @stephrobert — merged
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 85/100
Research direction
Read _confirmer in cli/progression.py:166-182 and compare how clean and reset handle confirmation without a terminal. Trace the destroy command's confirmation path and check how it reports the missing terminal and --yes. Done when destroy shows confirmation_sans_terminal and exits with code 2 in that case.
Written by the indexing model from the issue text.
Description
What happened
Lancés sans terminal (CI, script, entrée redirigée) et sans --yes,
clean et reset disent pourquoi la confirmation est impossible et
nomment --yes, puis sortent en code 2 (_confirmer,
cli/progression.py:166-182, chaîne confirmation_sans_terminal).
destroy affiche sa question puis « Aborted. » et sort en code 1, sans
raison ni mention de --yes.
Mesuré le 2026-11-09 avec 0.8.0 :
$ dsoxlab destroy < /dev/null
Détruire toute l'infrastructure du provider kvm ? Les données des VM seront perdues [y/N]: Aborted.
$ echo $?
1
Attendu
destroy passe par le même _confirmer : message
confirmation_sans_terminal, code 2.
- Dominant language
- Python
- Stars
- 109
- Forks
- 5
- Avg merge
- 15h 30m
- Merged PRs (30d)
- 32
Getting set up
- No Dockerfile or Docker Compose file
- Has a pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from stephrobert/dsoxlab
-
validate-structure n'affiche que sa conclusion : ni le lab, ni le champ, ni la raison du défautOpenbug
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
stephrobert/dsoxlab#335 ·
Maintainers usually reply within 1 day
-
bug
Difficulty 5/5 Over a week Newbie friendliness 36/100
stephrobert/dsoxlab#358 · 1 comment ·
Maintainers usually reply within 1 day
-
bug
Difficulty 4/5 3-5 days Newbie friendliness 48/100
stephrobert/dsoxlab#357 ·
Maintainers usually reply within 1 day
-
Difficulty 5/5 Over a week Newbie friendliness 15/100
stephrobert/dsoxlab#338 ·
Maintainers usually reply within 1 day
-
Difficulty 5/5 Over a week Newbie friendliness 18/100
stephrobert/dsoxlab#337 ·
Maintainers usually reply within 1 day
All issues in stephrobert/dsoxlab
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 77/100
Significant-Gravitas/AutoGPT#16733 ·
Maintainers usually reply within 1 day
-
changelog investigate
Difficulty 1/5 Under an hour Newbie friendliness 74/100
ramnes/notion-sdk-py#444 ·
-
documentation
Difficulty 2/5 1-3 hours Newbie friendliness 69/100
Judgment-Pack/judgment-pack-spec#299 ·
Maintainers usually reply within 1 day
-
Difficulty 1/5 Under an hour Newbie friendliness 90/100
QuantConnect/Documentation#2858 ·
Maintainers usually reply within 1 day
-
good first issue
Difficulty 2/5 1-3 hours Newbie friendliness 90/100
btclib-org/btclib#3047 ·
Maintainers usually reply within 1 day