-
-
Notifications
You must be signed in to change notification settings - Fork 2.1k
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
AI DeepSeek 422 Unprocessable Entity #14347
Comments
Please provide the complete log. ps: I guess it may be a docker network configuration problem. |
一样的问题 这就是全部日志 |
I have the same issue~ |
This entry of log is the only one that is related to AI failure. The other logs are unrelated. Please set up a container yourself, it is very easy to reproduce. |
actually, just the Aliyun API has this issue, if using Siliconflow API then it will be fine |
Thanks for the information. It is possible that the Aliyun API is incompatible with the OpenAI API specification in some details. We cannot change this. Thanks for your feedback and discussion. |
As stated, it works in windows client, not in docker. This seems like an platform dependent implementation error instead of an error from aliyun from my perspective. |
The implementation code of this part has nothing to do with the specific platform and is the same code. |
I tried another AI provider: https://api.deepinfra.com/v1/openai Not sure why this ticket is closed. Could you verify it before closing it? This should be very easy to verify. Just put in any provider in a docker container frontend. You will see the error. |
I tested https://api.deepseek.com/v1 with SiYuan Docker and it is available. The configuration is as follows: I think you could try changing this |
超时时间改成600试试 |
不行,一样的错 |
你用的是 ai 的哪个功能? |
就问了 “你好” |
终于知道怎么重现了,真不容易 随便填个错误的key,然后用一次,会报错,再把key改回正确的,还是会报错 重启docker后就不报错了 推测应该是缓存问题 |
只要报一次错,以后无论配置哪家的AI都会报错 |
Thanks for the trick, I rebooted my container by purging it and force recreate, it now works with the
Really not sure why a failure can persist. |
@sz2013 找到问题了,DeepSeek 不支持 content 为空字符串,这个问题下个版本解决,感谢反馈。 |
@phdbbs Please upgrade to the latest SiYuan |
AI Error in docker container: Invalid type for 'messages.[3].content'
Is there an existing issue for this?
Can the issue be reproduced with the default theme (daylight/midnight)?
Could the issue be due to extensions?
Describe the problem
Expected result
Should work regardless of platform.
Screenshot or screen recording presentation
Version environment
Log file
More information
Not sure why docker version does not work. Is it because of the networking is different for docker? Does the user need to config something such as DNS to make it work?
The text was updated successfully, but these errors were encountered: