David

there is probably something wrong in an html file somewhere or in some configuration somewhere from nginx some dangling character which is causing something to fail the build on the front-end. and in the end al the static assets (javascript, etc) instead of working properly you are just receiving index.html for all of them (you can confirm this in the network tab)

Yes... I think this will be up to us as engineers to fight against it else we will just end up being replaced by others who are able to not have any fun

ive been using cursor to start an initial solution (and by initial I mean it really works fully) and then I manually refactor and read every single line. but I can that in 1 or 2 years from now.. code quality will start to be worse and worse over time. and then you will have a bunch of highly senior engineers trying to understand what happening with their AI code 😅

has this been implemented?

just to confirm my intuition regarding the evals thing: I'm assuming that these "no llm call" evals can probably be run at the same time you send a trace to phoenix but if you want these more expensive llm evals (like the hallucinate and so on) you do it manually by running some code every once in a while? or do you do it for every llm trace you send?

we use this openinference and are doing it with bedrock but it doesnt look very good. everything is flat and we loose the custom attributes like the session_id.

I will take a careful look

Thank you! 🙇