aws / aws/amazon-q-developer-cli
Login issue
- 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
macOS 26.0.1 (25A362)
### Expected behaviour
I have give a prompt and it should work
### Actual behaviour
Kiro is having trouble responding right now:
0: Failed to send the request: An unknown error occurred: profileArn is required but no profiles are available. Please log in and select a profile.
1: An unknown error occurred: profileArn is required but no profiles are available. Please log in and select a profile.
Location:
crates/chat-cli/src/cli/chat/mod.rs:1647
BACKTRACE
5 frames hidden
6: chat_cli::cli::chat::ChatSession::next::{{closure}}::hc08e842fabddce93
at :
7: chat_cli::cli::chat::ChatSession::spawn::{{closure}}::hf17791a3d90aa364
at :
8: chat_cli::cli::chat::ChatArgs::execute::{{closure}}::h9c780a84e5005bc4
at :
9: chat_cli::cli::RootSubcommand::execute::{{closure}}::h710aa0aed09e33a2
at :
10: chat_cli::cli::Cli::execute::{{closure}}::hfa9e7bf6ef2f8672
at :
11: tokio::runtime::park::CachedParkThread::block_on::h9d1ad2839b00b14b
at :
12: tokio::runtime::context::runtime::enter_runtime::h1c4ac1708072c99c
at :
13: tokio::runtime::runtime::Runtime::block_on::h5132c123deef87ff
at :
14: chat_cli::main_inner::h06ef5e2ad80fce93
at :
15: std::sys::backtrace::__rust_begin_short_backtrace::h616bc8b432148992
at :
16: core::ops::function::FnOnce::call_once{{vtable.shim}}::ha5428312895ccf0e
at :
17: std::sys::thread::unix::Thread::new::thread_start::h98270432b6aefc44
at :
18: __pthread_cond_wait
at :
Run with COLORBT_SHOW_HIDDEN=1 environment variable to disable frame filtering.
Run with RUST_BACKTRACE=full to include source snippets.
### Steps to reproduce
_No response_
### Environment
```yaml
[q-details]
version = "1.28.2"
hash = "27868a6e6508e32a80d15e6eba2f6adbab6c2aa7"
date = "2026-03-27T00:14:48.847531Z (1d ago)"
variant = "full"
[system-info]
os = "macOS 26.0.1 (25A362)"
chip = "Apple M1"
total-cores = 8
memory = "8.00 GB"
[environment]
cwd = "/Volumes/Extreme SSD/Projects/Limber"
cli-path = "/Volumes/Extreme SSD/Projects/Limber"
os = "Mac"
shell-path = "/bin/zsh"
shell-version = "5.9"
terminal = "VSCode"
install-method = "unknown"
[env-vars]
PATH = "/Users/USER/.antigravity/antigravity/bin:/opt/homebrew/Cellar/openjdk@17/17.0.14/libexec/openjdk.jdk/Contents/Home/bin:/Users/USER/Library/Android/sdk/tools/bin:/Users/USER/Library/Android/sdk/tools:/Users/USER/Library/Android/sdk/platform-tools:/Users/USER/.pyenv/shims:/Users/USER/.pyenv/shims:/Users/USER/.nvm/versions/node/v18.18.2/bin:/Users/USER/development/flutter/bin:/opt/homebrew/bin:/usr/local/bin:/System/Cryptexes/App/usr/bin:/usr/bin:/bin:/usr/sbin:/sbin:/var/run/com.apple.security.cryptexd/codex.system/bootstrap/usr/local/bin:/var/run/com.apple.security.cryptexd/codex.system/bootstrap/usr/bin:/var/run/com.apple.security.cryptexd/codex.system/bootstrap/usr/appleinternal/bin:/Library/Apple/usr/bin:/Users/USER/development/flutter/bin:/Users/USER/Library/Application Support/Code/User/globalStorage/github.copilot-chat/debugCommand:/Users/USER/Library/Application Support/Code/User/globalStorage/github.copilot-chat/copilotCli:/Users/USER/.local/bin:/Users/USER/Library/Android/sdk/emulator:/Users/USER/Library/Android/sdk/platform-tools:/Users/USER/.local/bin:/Users/USER/.rvm/bin:/Users/USER/.local/bin"
QTERM_SESSION_ID = "95d2090d7f544b53b9af7a5d75905ffb"
Q_SET_PARENT_CHECK = "1"
Q_TERM = "1.28.2"
SHELL = "/bin/zsh"
TERM = "xterm-256color"
ZDOTDIR = "/Users/USER"
__CFBundleIdentifier = "com.microsoft.VSCode"
```
Guida per i contributori
Apri la guida per i contributori
Direzione di ricerca
Inizia da crates/chat-cli/src/cli/chat/mod.rs:1647 e riproduci il fallimento dopo aver eseguito q doctor e q restart. Poi traccia la relazione tra il login, la selezione del profilo e l’errore segnalato “profileArn is required”. L’issue non fornisce passaggi per la riproduzione né una definizione precisa di done, quindi la correzione prevista deve essere chiarita prima dell’implementazione.
Scritto dal modello di indicizzazione a partire dal testo della issue.
Valutazione
- Stack tecnologico
- macos, rust
- Ambito
- authentication, cli
- Tipo di issue
- Bug
- Difficoltà
- 4/5
- Tempo stimato
- 3-5 giorni
- Stato di attività
- Tranquilla
- Chiarezza
- Da chiarire
- Idoneità per principianti
- 35/100