-
Notifications
You must be signed in to change notification settings - Fork 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
[FEAT]查看历史对话所使用的 model 名称 #240
Comments
Title: About dialog display information and a bug After the conversation switches to a model conversation, I check the historical conversation. I can't see which model was used in the historical conversation. I wonder if it can be optimized. There is also a bug. Directly entering or refreshing the The project is very good and has been commercially supported. |
{"code":1001,"message":"登陆失效~"} |
{"code":1001,"message":"Login failed~"} |
啊?我是商业版,在设置里面 刷新网页就这样了。提示是纯json |
ah? I'm on the business version. I refreshed the webpage in the settings and that's it. The prompt is pure json |
截图 |
就是说没通过css报错提示,而是返回的响应体就是只有这一个json |
screenshot |
That is to say, no error message is reported through css, but the response body returned is only this json |
这个我完全可以确定不是这里的报错 |
I am absolutely certain that this is not an error reported here. |
ok。我自己排查一下。那这个issue就当作显示models的申请吧。 |
OK. I'll check it out myself. Then treat this issue as an application to display models. |
你看看你的nginx 反代或者waf什么的有没有什么问题 |
Check if there is any problem with your nginx reverse generation or waf etc. |
嗯,我也想到了,如果不是项目的问题,估计是反代出问题了,因为从主页进来,没有重新请求地址,只是静态显示的路径。刷新请求异常应该就是我自己nginx的问题。 |
Well, I also thought that if it is not a problem with the project, it is probably a problem with the reverse generation, because when entering from the home page, the address is not requested again, but the path is displayed statically. The refresh request exception should be my own nginx problem. |
对话切换模型对话后,查看历史对话,没办法看到历史对话用的哪个模型,不知道能不能优化一下。
另外有一个bug,直接进入或者刷新
/admin/system
界面 会提示{"code":1001,"message":"登陆失效~"}
。而返回主页是登录状态。好像是只能从主页进入才会携带token。应该是bug吧?项目很不错,已商业支持。
The text was updated successfully, but these errors were encountered: