-
Notifications
You must be signed in to change notification settings - Fork 2.5k
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
Responses Sent to Wrong Chat When Switching Between Chat History #942
Comments
@santistelus Can you confirm you are still experiencing this bug? Also, were you experiencing this locally or in a deployed app? Thanks. |
Hi @iseabock Yes, i am still experiencing this bug... and it is happening in both environments, locally and in a deployed app. |
@santistelus Can you make a screen recording of this? I'm having some trouble reproducing this bug. |
@iseabock Here! Chatbot.Issue.mp4 |
Thanks for the screen recording @santistelus. I suspect this may be a side effect of customizations that have been made in your app. I am not able to get the same behavior that you are getting. In the video I have provided, although I do see the "Generating answer" message when I switch the previous chat (a bug I'll fix :)) I am brought back to the second chat when the response is generated. Recording.2024-06-27.160931.mp4 |
I see... well do you mind sharing with me which file should i Review or any suggestions to solve this. :) |
I think the files to check would be Chat.tsx and Answer.tsx and take a look at any async issues around |
This issue is stale because it has been open for 30 days with no activity. |
When sending a message in a chat and switching to another chat from the history before the response is received, an error occurs. The error is that the response from the initial chat is displayed in the second chat.
Steps to reproduce the behavior:
Expected behavior
Responses should only be shown in the chat where the prompt was made.
Configuration: Please provide the following
The text was updated successfully, but these errors were encountered: