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
Cody extension breaks and displays only a grey window when loading history.
The workaround seems to only be to create a new chat then attempt to re-open the history, however even after 1 single attempt to interact with loaded history causes Cody to crash again and only display a grey window.
VS Code Version: 1.96.0
Cody Extension Version: 1.50.0
Expected behavior
Cody extension should not crash with a grey window on loading chat history or attempting to interact with chat history.
Alternatively, allow users to continue the chat history with full history context in a new chat window so it remains functional.
Additional context
OS: Linux
No response
The text was updated successfully, but these errors were encountered:
OS: Linux
Kernel: 6.11.8
Distribution: KDE Neon (Debian Based)
VS Code Install Repository: Microsoft Repo
Chat History Items: 15
If I export history, the exported JSON file's line count is approx: 2007881.
However when I open one specifically large chat history item from the 15 items, it does not show any specific message count, but whole window immediately does go grey as shown in the above screenshot.
Version
1.50.0
Describe the bug
Cody extension breaks and displays only a grey window when loading history.
The workaround seems to only be to create a new chat then attempt to re-open the history, however even after 1 single attempt to interact with loaded history causes Cody to crash again and only display a grey window.
VS Code Version: 1.96.0
Cody Extension Version: 1.50.0
Expected behavior
Cody extension should not crash with a grey window on loading chat history or attempting to interact with chat history.
Alternatively, allow users to continue the chat history with full history context in a new chat window so it remains functional.
Additional context
OS: Linux
No response
The text was updated successfully, but these errors were encountered: