search

epam / ai-dial-chat

A default UI for AI DIAL
https://chat.lab.epam.com
Apache License 2.0
57 stars 24 forks source link

After migration of chat from 0.4 to 0.6.12 if a user has super long conversations they become corrupted during conversation migration process #1109

Open photonn opened 5 months ago

photonn commented 5 months ago

EPAM AI DIAL chat version

0.6.12

How to reproduce

If you have a really long conversation, this gets corrupted during the migration of conversations from old 0.4 format to new 0.6: If you try to use the conversation again, you see this error:

This is the report from the client--> XXXXX and XXXXX were experiencing issues with using the dial chatbot. I discovered that they were not following the best practice for using the chatbot, which we need to make clearer in the future. They were using only one conversation for everything and had one long conversation for all prompts, which may have exceeded the overall length limit of a conversation inside dial. Additionally, it is possible that the issue may have started after a DIAL update on Monday, which could have corrupted old conversations if they were very long. To solve the problem, I simply suggested that they start a new conversation.

When the new update was implemented on Monday, all conversation were migrated to the new Dial Platform. If I remember correctly a suffix was added to our conversation with the same name. Maybe there is an issue with old and long conversation so that they get corrupted after the update.

Actual result

Long conversations are corrupted

Expected result

Long conversations are migrated without issues

Confidential information

mikitabut commented 5 months ago

Hello @photonn Do you have access to logs of chat? Maybe you see any of errors connected with completion?

photonn commented 5 months ago

@mikitabut No because they C level execs and there is lots of confidential info in those conversations, but they added extra info today:

"Prior to the current Dial platform update, when entering a too long text or having a too long conversation, a warning message reading how many characters were already entered and how many are allowed was showed. Now, only the generic error attached is shown when entering more than 30k characters. Please implement again the warning with the number of characters and the maximum number of characters allowed. "

I think they are separated issues but related.