billytrend-cohere

Results 17 comments of billytrend-cohere

Streamed events arrive all at once, _after_ generation is all done

Hey @sevaseva and @dsinghvi thanks for the detail here! I will take a look into the issue. I'd imagine your hypothesis about caching is correct. Perhaps nextjs needs to read...

Streamed events arrive all at once, _after_ generation is all done

Yeah without repro'ing I think what is happening is that nextjs is [revalidating](https://nextjs.org/docs/app/building-your-application/caching#revalidating-1) the streamed request by reading the whole body and checking if it is still the same which...

Streamed events arrive all at once, _after_ generation is all done

Hey @sevaseva we now send a no-cache header in our chat streaming response! Would love to hear if it solved your problem. Thanks

UTF-8 streams might break in current stream implementation

Hey @lazydogP many thanks for this interesting find! We have repro'd it and will have a fix for you asap.

UTF-8 streams might break in current stream implementation

@lazydogP we're planning to move to SSE to fix this issue for you! thanks for your patience

UTF-8 streams might break in current stream implementation

Hey all, this issue is now resolved in our v2 chat because we have switched to SSE which makes it easier to parse the streams. You can use it as...

Streamed events arrive all at once, _after_ generation is all done

I'm going to close this for now since there's a work around and we think it's fixed in prod > The non-streaming endpoints don't sent no-cache? we did fix the...

Pydantic V2 warning

Thanks @n1lanjan we are looking into this!

Pydantic V2 warning

This is now fixed in the latest version of the sdk! thanks @n1lanjan

Pydantic V2 warning

Thanks for the repro @Tenzer, looking into it!