Skip to content

Conversation

@MehakBindra
Copy link
Contributor

@MehakBindra MehakBindra commented Oct 16, 2025

Issue : #374

Main change::

  • In emit, instead of cancelling and scheduling a new timeout,
    - flush immediately if no timeout pending,
    - else push to queue and wait.
Screen.Recording.2025-10-16.140937.mp4

Devtools: Streaming always starts before the full response is received (check with logs, see attached video).
Teams: Even though the first chunk is emitted immediately, (sometimes) by the time the stream starts on Teams, the full response is ready. In the second msg, we can see the stream starts a little bit before the full response is printed.

@MehakBindra MehakBindra changed the title [Fix] Do not reset timeout for each chunk emit [Fix] streaming: do not reset timeout for each chunk emit Oct 16, 2025
Copy link
Collaborator

@heyitsaamir heyitsaamir left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Makes sense to me. Talked to Mehak offline about this too. @aacebo can you take a look too?

@aacebo
Copy link
Collaborator

aacebo commented Oct 24, 2025

@MehakBindra can you add some tests around this area?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants