Deepseek Service Woes

At a glance

Related to my previous thread on the timeout bug, it looks like it wouldnt matter even if the bug is fixed, because when they are having issues, deepseek returns in 60 seconds, with an 200 OK, but an empty response. While at the same time indicating that the response is in json. Which breaks in the openai library here, since there is no check to see if what is returned is actually json.

But since this is a deepseek issue which is an openai like api, fixing it's going to probably take a fork of the openai api, or handle it elsewhere. sigh

5 comments

rro

@Logan M is it possible to override the openai like (or the recent deepseek llm lib) to use a forked version of the openai library - but keep using the official openai lib in other places?

LLogan M

I think you'd just have to pip install your forked version

rro

But if I want to use both? One for everything except for deepseek, the other only for deepseek.

LLogan M

hmmm, youd have to change the name of your forked package (and also change imports) -- that gets a little more complicated

LLogan M

I don't think your forked version should change how other non-deepseek models work? Aren't you just checking for the timeout?

Add a reply

Find answers from the community

Deepseek Service Woes