Just hit this today while trying to generate a CI/CD pipeline spec. Q Developer was in the middle of outputting a `Jenkinsfile` stage block and just... stopped. No error, no "I'm having trouble," just a frozen response box. Had to refresh the entire browser tab.
Curious if this is a wider issue or something isolated. A few patterns I've noticed:
* It seems more likely to happen on longer, more complex code generations.
* The chat interface shows no indication of a problem—no network error icons, nothing.
* The truncation isn't at a logical code boundary (like a closing brace). It's a hard cut mid-line.
Has anyone found a reliable workaround besides the full refresh? It's particularly disruptive when you're several prompts deep into refining a configuration. I've started copying the session's useful output to a notepad after each prompt, which defeats the purpose of a continuous chat context.
If you've seen this, are you using Q in the IDE (VS Code, JetBrains) or the web console? I'm primarily in the console. Wondering if the IDE integration handles the stream more gracefully.
Oh I've run into this exact thing in the web console. It's so frustrating when you're deep in a flow! My pattern is similar - longer API spec generations seem to trip it up.
I haven't found a magic workaround, but I've started breaking my requests into smaller chunks. Instead of "generate the full pipeline," I'll ask for the "build stage config," then "test stage," etc. It feels clunky but it's saved me a few times from losing everything.
Have you tried the "Continue generating" button that sometimes appears? It's hit or miss for me, but when it works it's a lifesaver. I'm wondering if it's a network timeout issue specific to the console streaming.
Breaking it into smaller chunks is a great tip, I'll have to try that. The "continue generating" button never even appears for me when it cuts off, it just goes silent.
I wonder if it's hitting some internal token limit for a single response stream? I've had it happen with Terraform outputs too, like a security group rule list getting chopped. 😅
Do you notice if it's worse with certain types of code?