aws / aws/amazon-q-developer-cli

Amazon Q CLI unexpected error/timeout after 151.44s

オープン
#1,971 コメント 1 件 リアクション 0 件 担当者 0 名 GitHub で見る
bug
主要言語
Rust
スター
2k
フォーク
439
PR マージ指標
30日以内にマージされた PR はありません

説明

### 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_

コントリビューションガイド

コントリビューションガイドを開く

調査の方向性

ソースファイル、テスト、エントリポイントのいずれも指定されておらず、報告には再現手順もありません。まず、大きなリクエストを使用して macOS 15.5 でタイムアウトを再現し、報告された request ID を使って調査してください。クライアントのタイムアウトなのか、モデルまたはサービスの障害なのか、それともエラーメッセージの不足なのかを特定できれば完了です。

索引モデルが issue の本文から書いたものです。

評価

技術スタック
rust
領域
ai, cli
issue の種類
バグ
難易度
4/5
見積もり時間
3〜5日
活発さ
停滞
明瞭さ
説明が足りない
初心者へのやさしさ
25/100

新しい issue をメールで受け取る

初心者向けの GitHub issue を短くまとめたダイジェスト。