-
Notifications
You must be signed in to change notification settings - Fork 16
Support non streamed responses #3
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
🎁 Share your feedback on Copilot Code Reviews and get GitHub Shop credit!
- Complete this short 3 minute survey and tell us how we can improve Copilot Code Reviews for you and your team.
- Leave feedback on Copilot's comments using the 👍 and 👎 buttons on each review comment, and you could be one of 3 Hubbers to win a $50 GitHub Shop credit.
itsbagpack
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think the logic and structure makes sense! Left a couple of questions more around my lack of knowledge around this neck of the woods 😆
Models like o1 require non-streamed responses. To make that work, I've introduced a common interface that lets us treat these like normal streamed responses (with one large chunk). I've also had to tweak the consuming code to accept data either from
.Deltaor.Message, since non-streamed responses will use.Message.While I'm here, I've added some more explicit instructions about developing/releasing this locally.