aws / aws/amazon-q-developer-cli
Error on 'update'
- Lingua principale
- Rust
- Stelle
- 2k
- Fork
- 439
- Metriche di merge delle PR
- Nessuna PR unita negli ultimi 30g
Descrizione
### Checks
- [x] I have searched [github.com/aws/amazon-q-developer-cli/issues](https://github.com/aws/amazon-q-developer-cli/issues?q=) and there are no duplicates of my issue
- [x] I have run `q doctor` in the affected terminal session
- [x] I have run `q restart` and replicated the issue again
### Operating system
Linux 6.6.87.2-microsoft-standard-WSL2 - Ubuntu 24.04.3 LTS
### Expected behaviour
Kiro-cli updates on `kiro-cli update`
### Actual behaviour
Error indicating to run doctor. Running doctor returns success. Update still results in an error.
```bash
➜ ~ q update
░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░ 0/100error: failed to update: `Update is only supported for binaries installed in "/home/justirus/.local/bin", the current executable is in "/home/justirus/.toolbox/tools/kiro-cli/1.24.1"`
If this is unexpected, try running kiro-cli doctor and then try again.
➜ ~ kiro-cli doctor
● /home/justirus/.bashrc does not source pre integration
● /home/justirus/.profile does not source pre integration
✘ zsh ~/.zshrc integration check: /home/justirus/.zshrc does not source post integration last
Run kiro-cli integrations install dotfiles to reinstall shell integrations for zsh
Attempting to fix automatically...
Re-running check...
✔ zsh ~/.zshrc integration check
✔ Everything looks good!
Kiro CLI still not working? Run kiro-cli issue to let us know!
➜ ~ kiro-cli update
░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░ 0/100error: failed to update: `Update is only supported for binaries installed in "/home/justirus/.local/bin", the current executable is in "/home/justirus/.toolbox/tools/kiro-cli/1.24.1"`
If this is unexpected, try running kiro-cli doctor and then try again.
```
### Steps to reproduce
1. type `kiro-cli update`
### Environment
```yaml
[q-details]
version = "1.24.1"
hash = "ffce156030f05d9cec3d4817c3a64245a967db74"
date = "2026-01-27T20:40:33.213575Z (9d ago)"
variant = "minimal"
[system-info]
chip = "Intel(R) Core(TM) Ultra 7 265U"
total-cores = 7
memory = "15.34 GB"
[system-info.os.linux]
kernel_version = "6.6.87.2-microsoft-standard-WSL2"
id = "ubuntu"
name = "Ubuntu"
pretty_name = "Ubuntu 24.04.3 LTS"
version_id = "24.04"
version = "24.04.3 LTS (Noble Numbat)"
[environment]
cwd = "/home/USER"
cli-path = "/home/USER"
os = "Linux"
shell-path = "/usr/bin/zsh"
shell-version = "5.9"
install-method = "toolbox"
in-wsl = true
[env-vars]
DISPLAY = ":0"
PATH = "/home/USER/.aim/mcp-servers:/home/USER/.nvm/versions/node/v24.13.0/bin:/home/USER/.pyenv/shims:/home/USER/.pyenv/bin:/home/USER/.local/bin:/home/USER/.toolbox/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/usr/local/games:/usr/lib/wsl/lib:/mnt/c/Program Files/itacsvc:/mnt/c/WINDOWS/system32:/mnt/c/WINDOWS:/mnt/c/WINDOWS/System32/Wbem:/mnt/c/WINDOWS/System32/WindowsPowerShell/v1.0/:/mnt/c/WINDOWS/System32/OpenSSH/:/mnt/c/Program Files/dotnet/:/mnt/c/Program Files/PuTTY/:/mnt/c/Program Files/Common Files/AmazonMidwayClientSuite/bin/:/mnt/c/Program Files/Amazon/FOPAzureADMAnagementApp/:/mnt/c/Program Files (x86)/Quarantine:/mnt/c/Program Files (x86)/Quarantine/:/mnt/c/Program Files/Amazon/Guardian/:/mnt/c/Users/USER/AppData/Local/Microsoft/WindowsApps:/mnt/c/Users/USER/AppData/Local/Programs/Microsoft VS Code/bin:/home/USER/.local/bin"
QTERM_SESSION_ID = "4f3a566277744e75b6b3470ffecad6f3"
Q_SET_PARENT_CHECK = "1"
Q_TERM = "1.24.1"
SHELL = "/usr/bin/zsh"
TERM = "xterm-256color"
```
Guida per i contributori
Apri la guida per i contributori
Direzione di ricerca
Inizia riproducendo `kiro-cli update` con il metodo di installazione Toolbox mostrato nel report, quindi traccia il modo in cui il comando di aggiornamento gestisce il percorso dell’eseguibile corrente. Confronta questo comportamento con il percorso documentato `/home/USER/.local/bin` e l’output di `doctor`. Il lavoro è completato quando l’installazione segnalata può essere aggiornata correttamente oppure il comando spiega chiaramente il percorso di aggiornamento supportato.
Scritto dal modello di indicizzazione a partire dal testo della issue.
Valutazione
- Stack tecnologico
- rust
- Ambito
- cli, devtools
- Tipo di issue
- Bug
- Difficoltà
- 3/5
- Tempo stimato
- 1-2 giorni
- Stato di attività
- Ferma
- Chiarezza
- Abbastanza chiara
- Idoneità per principianti
- 35/100