aws / aws/amazon-q-developer-cli

Kiro is having trouble responding right now:

Offen
#3,701 1 Kommentar 0 Reaktionen 0 zugewiesene Personen Auf GitHub ansehen
Vorherrschende Sprache
Rust
Sterne
2k
Forks
439
PR-Merge-Kennzahlen
Keine gemergten PRs in 30 T.

Beschreibung

### 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.14.0-37-generic - Linux Mint 22.3

### Expected behaviour

i have have bought kiro pro two days ago im not happy with the support here is the error i expect response in 2 days: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 omitted. Run with RUST_BACKTRACE=1 environment variable to display it.
Run with RUST_BACKTRACE=full to include source snippets.

i have re logged in it didnt work

Image

### Actual behaviour

Image

### Steps to reproduce

_No response_

### Environment

```yaml

[q-details]
version = "1.28.2"
hash = "27868a6e6508e32a80d15e6eba2f6adbab6c2aa7"
date = "2026-03-27T00:12:46.489292Z (2d ago)"
variant = "minimal"

[system-info]
chip = "AMD Ryzen 5 5600X 6-Core Processor"
total-cores = 6
memory = "31.27 GB"

[system-info.os.linux]
kernel_version = "6.14.0-37-generic"
id = "linuxmint"
name = "Linux Mint"
pretty_name = "Linux Mint 22.3"
version_id = "22.3"
version = "22.3 (Zena)"

[environment]
cwd = "/home/USER"
cli-path = "/home/USER"
os = "Linux"
shell-path = "/usr/bin/bash"
shell-version = "5.2.21"
terminal = "Gnome Terminal"
install-method = "unknown"

[env-vars]
DISPLAY = ":0"
GTK_IM_MODULE = "ibus"
PATH = "/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/usr/local/games:/snap/bin:/home/USER/.local/bin"
QTERM_SESSION_ID = "981d3ee75ddb4f2db9cf3e7aa40aeb2f"
QT_IM_MODULE = "ibus"
Q_SET_PARENT_CHECK = "1"
Q_TERM = "1.28.2"
SHELL = "/bin/bash"
TERM = "xterm-256color"
XDG_CURRENT_DESKTOP = "X-Cinnamon"
XDG_SESSION_DESKTOP = "cinnamon"
XDG_SESSION_TYPE = "x11"
XMODIFIERS = "@im=ibus"
```

Beitragsleitfaden

Beitragsleitfaden öffnen

Rechercherichtung

Beginnen Sie bei crates/chat-cli/src/cli/chat/mod.rs:1647 und prüfen Sie den nach q doctor und q restart gemeldeten Request-Fehler. Reproduzieren Sie den profileArn-Fehler unter Linux Mint 22.3 mit Version 1.28.2 und überprüfen Sie anschließend, dass ein angemeldeter Benutzer mit einem ausgewählten Profil eine Antwort ohne den Fehler empfangen kann.

Vom Indexierungsmodell aus dem Issue-Text verfasst.

Bewertung

Tech-Stack
aws, linux, rust
Bereich
authentication, cli
Issue-Typ
Bug
Schwierigkeit
3/5
Geschätzter Aufwand
1-2 Tage
Aktivitätsstatus
Ruhig
Klarheit
Größtenteils klar
Anfängerfreundlichkeit
38/100

Neue Issues direkt in Ihr Postfach

Eine kurze Übersicht über anfängerfreundliche GitHub-Issues.