You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Sometimes, a few conversations on the left sidebar can be clicked, but clicking on them will have no effect. I have experienced this several times, but unfortunately, I still cannot reproduce this bug. In fact, I checked the indexedDB and find those conversations not in the messages db.
I think this issue may be related to the fact that messages and conversation metadata are saved in two different indexedDBs. This may work fine most of the time, but if the data in these two indexedDBs becomes inconsistent (possibly due to interruption during the storage process), then those "zombie conversations" cannot be deleted unless I manually check and modify indexedDB in DevTools.
What provider are you using?
OpenAI
What prompt did you enter?
No response
Console Logs
No response
Participation
I am willing to submit a pull request for this issue.
The text was updated successfully, but these errors were encountered:
What operating system are you using?
Windows
What browser are you using?
Chrome
Describe the bug
Sometimes, a few conversations on the left sidebar can be clicked, but clicking on them will have no effect. I have experienced this several times, but unfortunately, I still cannot reproduce this bug. In fact, I checked the indexedDB and find those conversations not in the messages db.
I think this issue may be related to the fact that messages and conversation metadata are saved in two different indexedDBs. This may work fine most of the time, but if the data in these two indexedDBs becomes inconsistent (possibly due to interruption during the storage process), then those "zombie conversations" cannot be deleted unless I manually check and modify indexedDB in DevTools.
What provider are you using?
OpenAI
What prompt did you enter?
No response
Console Logs
No response
Participation
The text was updated successfully, but these errors were encountered: