Skip to main content

Arize AI Community Icon

Home
Events

Arize AX Releases
Arize AX Support
Arize News
Arize Observe
Discussions
Introductions
Phoenix Support

Powered by Tightknit

Phoenix Support

Phoenix Support

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

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 <https://github.com/Arize-ai/phoenix/issues/4912|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 <https://github.com/Arize-ai/phoenix/issues/6114|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: - <https://github.com/Arize-ai/phoenix/issues/4912|GitHub issue #4912> - <https://github.com/Arize-ai/phoenix/issues/6114|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.