Long-running prompt suddenly hangs forever with no error or exception

[fantasyearl]

Each prompt request seems to have a maximum execution time. After that, the request hangs indefinitely and never completes.
If this behavior is intentional (e.g., to protect server-side resources), the documentation should mention this maximum execution time limit.
Also, the session should raise/throw a timeout exception instead of just hanging forever.
Not sure if this is related to issue #212.

Reproduction steps

1. Create a session and enable the streaming feature (so we can observe whether it's still "thinking" and producing output).
2. Ask it to perform an almost impossible task that forces it to keep trying repeatedly.
3. After roughly 1 hour, check whether it is still streaming any output.

In my case, I provided a custom car license plate detection dataset and asked it to find a pure OpenCV method to achieve 90% accuracy.

It started outputting progress (e.g., which method it decided to try and the resulting accuracy).
Then at some point, it simply hung and stopped streaming any further output.

[github-actions]

Thank you for opening this issue @fantasyearl!

I've labeled this as bug, documentation, and needs-info because:

• The hang without error/exception is unexpected behavior
• Timeout limits should be documented if they exist
• We need additional details to investigate

To help us reproduce and diagnose this issue, could you please provide:

1. Which SDK and version are you using? (Node.js, Python, Go, or .NET + version number)
2. Your code snippet showing how you created the session and sent the prompt
3. SDK/CLI logs if available - any relevant error messages or warnings before the hang
4. Exact duration when the hang occurred (you mentioned ~1 hour)
5. Behavior details:
   • Did the process hang completely or just stop producing output?
   • Could you cancel/interrupt it, or did you have to kill the process?
   • Any CPU/memory spikes observed?

While this may be related to #212 (session idle timeout), your issue appears to describe an execution timeout during an active streaming session, which is different. The additional information will help us determine if this is a timeout issue, a resource limit, or something else entirely.

AI generated by Issue Triage Agent