aws / aws/amazon-q-developer-cli

Amazon Q CLI unexpected error/timeout after 151.44s

Offen
#1,971 1 Kommentar 0 Reaktionen 0 zugewiesene Personen Auf GitHub ansehen
bug
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

### Operating system

macOS 15.5.0 (24F74)

### Expected behaviour

The Amazon Q CLI should complete the request without timing out or return a more specific error message with troubleshooting steps. Unable to support large complex requests causes connection to timeout.

### Actual behaviour

Received an unexpected error from the model after 151.44s with request_id: 5091af8e-59e4-45f2-a8a1-5be3cf36330b

```
[chat-transcript]
> how to resolve this Warning: received an unexpected error from the model after 151.44s>
request_id: 5091af8e-59e4-45f2-a8a1-5be3cf36330b

This error message indicates a timeout issue when communicating with an AI model. Let me help you troubleshoot this problem.

The "unexpected error from the model after 151.44s" suggests that your request to the model timed out after approximately 2.5 minutes. This can happen for several reasons when working with Quenzy's AI features.

Here are some steps to resolve this issue:

1. **Check your network connection**
- Ensure you have a stable internet connection
- Try connecting via a different network if possible

2. **Reduce request complexity**
- If you're sending large amounts of data to the model (like long transcripts or complex images), try reducing the size
- Break down complex requests into smaller chunks

3. **Update dependencies**
- Make sure your Node.js and npm packages are up to date
\```bash
npm update
\```

4. **Increase timeout settings**
- You may need to modify timeout settings in your application configuration

5. **Check service status**
- The AI service might be experiencing high load or outages
- Check the status page of the AI provider you're using

6. **Review logs**
- Check your application logs for more detailed error information:
\```bash
npm run logs
\```

7. **Retry with exponential backoff**
- Implement retry logic with increasing delays between attempts

If you need more specific help, could you provide additional context about what you were doing when this error occurred? For example, which AI feature in Quenzy were you using (transcription, sign language interpretation, etc.)?
[Tool uses: none]

> >
report issues for amazon q with bug

I'll help you report an issue for Amazon Q. Let me use the appropriate tool to open a GitHub issue template for you.
[Tool uses: report_issue]
```

### Steps to reproduce

_No response_

Beitragsleitfaden

Beitragsleitfaden öffnen

Rechercherichtung

Keine Quelldatei, kein Test und kein Einstiegspunkt werden genannt, und der Bericht enthält keine Schritte zur Reproduktion. Beginne damit, das Timeout unter macOS 15.5 mit einer großen Anfrage zu reproduzieren, und verwende die gemeldete request ID zur Untersuchung; abgeschlossen ist die Arbeit, wenn festgestellt wurde, ob es sich um ein Client-Timeout, einen Modell- oder Servicefehler oder eine Lücke in der Fehlermeldung handelt.

Vom Indexierungsmodell aus dem Issue-Text verfasst.

Bewertung

Tech-Stack
rust
Bereich
ai, cli
Issue-Typ
Bug
Schwierigkeit
4/5
Geschätzter Aufwand
3-5 Tage
Aktivitätsstatus
Veraltet
Klarheit
Muss geklärt werden
Anfängerfreundlichkeit
25/100

Neue Issues direkt in Ihr Postfach

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