aws / aws/amazon-q-developer-cli
bug:
- 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
Windows 11
### Expected behaviour
Amazon Q to work properly
### Actual behaviour
For many months now I can't use amazon Q on intelliJ
I tried to uninstall amazonQ and amz-core plugin a few times with no succes.
The amazon Q chat is blocked on "working..." when I type something and code whisperer keep on "loading" with no success.
So when I start intelliJ I got ~100 exception that looks like this :
`java.lang.IllegalStateException: Missing header Content-Length in input "}}Content-Length: 171
"
at org.eclipse.lsp4j.jsonrpc.json.StreamMessageProducer.listen(StreamMessageProducer.java:94)
at org.eclipse.lsp4j.jsonrpc.json.ConcurrentMessageProcessor.run(ConcurrentMessageProcessor.java:114)
at java.base/java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:572)
at java.base/java.util.concurrent.FutureTask.run(FutureTask.java:317)
at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1144)
at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:642)
at java.base/java.lang.Thread.run(Thread.java:1583)
`
Or
`java.lang.IllegalStateException: Missing header Content-Length in input "{"jsonrpc":"2.0","method":"window/logMessage","params":{"type":2,"message":"[2025-11-05T10:04:58.783Z] lserver: Agent config not found at c:\\Users\\f3j7mo\\git\\taoimm\\040_Realisation\\Developpement\\taoimm\\tao-imm-web\\.amazonq\\agents\\default.json, skipping."}}Content-Length: 194
"
at org.eclipse.lsp4j.jsonrpc.json.StreamMessageProducer.listen(StreamMessageProducer.java:94)
at org.eclipse.lsp4j.jsonrpc.json.ConcurrentMessageProcessor.run(ConcurrentMessageProcessor.java:114)
at java.base/java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:572)
at java.base/java.util.concurrent.FutureTask.run(FutureTask.java:317)
at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1144)
at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:642)
at java.base/java.lang.Thread.run(Thread.java:1583)
`
### Steps to reproduce
_No response_
### Environment
```yaml
Windows 11
Amazon Q 3.97.251
IntelliJ IDEA 2025.1.7 (but doesn't work from 2024)
```
Guida per i contributori
Apri la guida per i contributori
Direzione di ricerca
Inizia con l’integrazione IntelliJ e gli errori LSP mostrati nell’issue, quindi riproduci il comportamento su Windows 11 utilizzando le versioni elencate di Amazon Q e IntelliJ. Esegui `q doctor` e `q restart` nella sessione del terminale interessata e verifica se la chat si arresta su “working...” e CodeWhisperer su “loading”; il lavoro è completato quando l’integrazione funziona senza le eccezioni Content-Length segnalate.
Scritto dal modello di indicizzazione a partire dal testo della issue.
Valutazione
- Stack tecnologico
- java, rust
- Ambito
- devtools
- Tipo di issue
- Bug
- Difficoltà
- 4/5
- Tempo stimato
- 3-5 giorni
- Stato di attività
- Ferma
- Chiarezza
- Da chiarire
- Idoneità per principianti
- 25/100