fix: consume stream to prevent hanging

[dm-cohere]

This commit changed how the stream was closed, and means that clients can end up hanging after calling the stream.

---

Note

Ensure sync/async streaming drains remaining SSE events after [DONE] so the HTTP response closes without hanging.

• Streaming:
  • Update Stream.__stream__ and AsyncStream.__stream__ in src/groq/_streaming.py:
    • Remove try/finally immediate response close; instead drain the SSE iterator after encountering [DONE] to trigger connection closure.
    • Preserve error handling and data processing logic for normal and error events.

^{Written by Cursor Bugbot for commit 8ac6a76. This will update automatically on new commits. Configure here.}

[gradenr]

This issue has been in the code generator.

[cursor]

Bug: Stream not consumed when exception occurs during streaming

The removal of the try-finally block creates a bug where the stream-consuming code at the end of __stream__ (lines 98-100 for sync, 199-201 for async) is never reached if an APIError is raised during iteration. When an error SSE is received and APIError is raised, the exception propagates immediately without consuming the remaining stream, which could cause the same hanging issue this PR attempts to fix. The stream consumption logic needs to be wrapped in a try-finally to ensure it executes even when exceptions occur.

Additional Locations (1)

• src/groq/_streaming.py#L158-L201