Bug Report: Arize UI Trace Error with Codemirror Integration

·Feb 28, 2025 12:18 PM

Hi there - I have a bug to report in the Arize UI when opening any trace it immediately shows "An error occurred". Looks like a front-end error relating to Codemirror.

2 comments

· Sorted by Oldest

Phoenix Support

Bug Report: Arize UI Trace Error with Codemirror Integration

Neil M.

·Feb 28, 2025 12:18 PM

Hi there - I have a bug to report in the Arize UI when opening any trace it immediately shows "An error occurred". Looks like a front-end error relating to Codemirror.

2 comments

· Sorted by Oldest

RunLLM
APP
·
This issue might be related to a known bug where the UI errors out due to issues with Codemirror or other front-end components. According to the GitHub issue #4912, similar problems have been reported where the UI errors out when messages are badly formatted. Additionally, there have been other UI-related issues, such as the one mentioned in GitHub issue #6114, where switching to TypeScript code breaks the prompt index page.Would you like more details on how to potentially resolve this issue or further investigate the problem? Sources: - GitHub issue #4912 - GitHub issue #6114
💡 Hint: Mention RunLLM in the thread for followups.
Neil M.
·
Maybe, but all traces were generated with the llamaindex integration. I haven't generated any traces manually yet.

RunLLM
APP
·
This issue might be related to a known bug where the UI errors out due to issues with Codemirror or other front-end components. According to the GitHub issue #4912, similar problems have been reported where the UI errors out when messages are badly formatted. Additionally, there have been other UI-related issues, such as the one mentioned in GitHub issue #6114, where switching to TypeScript code breaks the prompt index page.Would you like more details on how to potentially resolve this issue or further investigate the problem? Sources: - GitHub issue #4912 - GitHub issue #6114
💡 Hint: Mention RunLLM in the thread for followups.
Neil M.
·
Maybe, but all traces were generated with the llamaindex integration. I haven't generated any traces manually yet.