-
Notifications
You must be signed in to change notification settings - Fork 9.7k
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
Ensure the 'inputs' field in /chat-messages takes effect every time #7955
Conversation
This PR does not resolve, using the conversation id to link to previous sessions but the input works |
I don't understand "using the conversation id to link to previous sessions but the input works". As for "This PR does not resolve", I have tried and I think it works. |
This PR is to make sure the 'inputs' field in the API "/chat-messages" takes effect every time, is that what you mean "using the conversation id to link to previous sessions but the input works"? |
Yes, you mean that the input field of the conversation can be updated under the same conversation, because the input is only effective when the conversation link is first established |
I noticed that both table 'messages' and table 'conversations' have an 'inputs' field. I think the 'inputs' field should be aligned with table 'messages'. The 'inputs' field in table 'conversations' may not be very useful. In this PR, the 'inputs' field in table 'conversations' means the 'inputs' in the first message, and the 'inputs' field in table 'messages' means the true inputs in this message. |
What's the mean of 'This PR does not resolve'? Is that any problems? |
This is the problem I encountered, maybe I understand wrong, this PR can't solve the problem of the video in issue? |
I understand that the conversation table input is valid for the first time. The message table is used for every subsequent interaction, right? |
right |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Excellent changes, making the workflow much more flexible.
I think it's great, too Hope to support this feature |
Has this feature not been merged? |
I don't know why they don't merge it, maybe we need more people to push them. |
I highly appreciate your functionality and have submitted a new issue. If they do not merge, I will download your branch |
any update ? |
i need this pr |
Happy New Year, but what? |
Happy New Year, everybody! @crazywoola @takatost @laipz8200 @iamjoel @JohnJyong @zxhlyh |
I'll revisit this with the team later, but we probably won't be releasing a minor update anytime soon, and we're working on a 1.0 update. |
We've already been waiting for five months, and we don't mind waiting a little longer, as long as it won't be another five months. |
hhhhhhhhhhhhhhhhhhh,maybe 5 years |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
LGTM |
when to merge? |
If we don't merge, I wonder if there's any way to add the DeepSeek R1 model. The current code is not easy to update.? |
This PR is not about the deepseek models, we provider many integrations of deepseek in the 0.15.3 version. Check the release note. |
Additionally, how can I switch between DeepSeek-R1 and DeepSeek-V3 models within a session, rather than using different applications to implement the switch? I noticed that the chat window on the DeepSeek official website allows switching between DeepSeek-R1 and DeepSeek-V3 |
Please merge this, we need this feature asap |
2 similar comments
Please merge this, we need this feature asap |
Please merge this, we need this feature asap |
Owners of Dify, please merge and release this. It's holding us back from using Dify. In the meantime, anyone know any other tools like Dify? |
maybe ragflow or fastgpt |
lgtm |
Great ! |
@crazywoola when will this be released? |
Checklist:
Important
Please review the checklist below before submitting your pull request.
dev/reformat
(backend) andcd web && npx lint-staged
(frontend) to appease the lint godsDescription
Describe the big picture of your changes here to communicate to the maintainers why we should accept this pull request. If it fixes a bug or resolves a feature request, be sure to link to that issue. Close issue syntax:
Fixes #<issue number>
, see documentation for more details.Close #7952
Close #7846
Close #8063
Close #8839
Close #8546
Close #10522
Close #10055
Close #10643
Close #13363
Type of Change
Testing Instructions
Please describe the tests that you ran to verify your changes. Provide instructions so we can reproduce. Please also list any relevant details for your test configuration