这是indexloc提供的服务,不要输入任何密码
Skip to content

Update ResponseBodyCallback.java,适配DeepSeek SSE keep-alive消息 Fixes #86 #87

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

Closed
wants to merge 0 commits into from

Conversation

ljia310
Copy link

@ljia310 ljia310 commented Feb 14, 2025

No description provided.

@ljia310 ljia310 changed the title Update ResponseBodyCallback.java,适配DeepSeek SSE keep-alive消息 Update ResponseBodyCallback.java,适配DeepSeek SSE keep-alive消息 Fixes #86 Feb 14, 2025
@Lambdua
Copy link
Owner

Lambdua commented Feb 14, 2025

首先 十分感谢你提交pq

@Lambdua
Copy link
Owner

Lambdua commented Feb 14, 2025

这里最好用else if把deepseek的返回数据单独处理。 else 中的throw 不要吞掉。 api要考虑更多的情况

@ljia310
Copy link
Author

ljia310 commented Feb 14, 2025

这个库主要是对接openai兼容的服务,肯定是应该严格按照openai的格式处理,所以下面的2个分支就是标准流程,其它流程就都可以认为是非标的。
deepseek服务现在是在openai标准格式基础上加了自己的特殊心跳数据包,有可能还有其它平台也会加其它的数据包,为了适应性更广,所以我选择直接在elase里面丢弃非openai的数据,因为丢掉这些特殊数据包,也不会影响正常openai的标准流程。
image

@Lambdua
Copy link
Owner

Lambdua commented Feb 14, 2025

非标也不应该被吞掉。 后续使用这个库的人排查错误会头大的

@ljia310
Copy link
Author

ljia310 commented Feb 14, 2025

OK,已经按建议对DeepSeek官网API服务的SSE 心跳数据做了特殊处理

@ljia310
Copy link
Author

ljia310 commented Feb 15, 2025

总觉得这样特殊处理的方式不够完美,以后又遇到其它厂家的特殊数据包,还得修改代码调整。
能不能把这个解码的过程开放,默认就是现在这样遇到非预期数据包直接抛异常,另外允许用户自行重写这个解码接口

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.

2 participants