You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The current implementation of --no-stream makes sense to some degree, i.e. the OpenAI response is not streamed. However, it doesn't make sense to render the 'ticker' that way - we have the full response in memory anyway.
It would also make sense to be able to toggle this dynamically:
.set stream true
.set stream false
The current --no-stream can be maintained and just set the config value (config.stream) to false.
I took a look at render/mod.rs:render_stream and render/repl.rs:repl_render_stream but don't have enough Rust experience to idiomatically solve this. My hunch is that there are two types of receivers ReplyStreamEvent and ReplyEvent. The writer is then either streamed or instant.
The text was updated successfully, but these errors were encountered:
The current implementation of
--no-stream
makes sense to some degree, i.e. the OpenAI response is not streamed. However, it doesn't make sense to render the 'ticker' that way - we have the full response in memory anyway.It would also make sense to be able to toggle this dynamically:
The current
--no-stream
can be maintained and just set the config value (config.stream
) to false.I took a look at
render/mod.rs:render_stream
andrender/repl.rs:repl_render_stream
but don't have enough Rust experience to idiomatically solve this. My hunch is that there are two types of receiversReplyStreamEvent
andReplyEvent
. The writer is then either streamed or instant.The text was updated successfully, but these errors were encountered: