#errors not showing up

1 messages · Page 1 of 1 (latest)

hybrid mauve
#

Ah looks like this happens when the error stems from an input

#

need to think about that. we haven't hit that scenario before, we only 'reveal' calls that the LLM makes, but in this case those values were passed in without the LLM making those calls itself

orchid epoch
#

oh lol I didn't even see that 😛

hybrid mauve
#

yeah, I had to click 'show noisy spans'

orchid epoch
#

OK I think I'm conflating several problems then. Yesterday I think the error didn't come from the inputs

hybrid mauve
#

or in TUI you could hold +

#

(but, shouldn't need to)

#

maybe we should sync all inputs and bail out early if any of them fail?

orchid epoch
#

I wanted to find last night's trace but dagger cloud won't let me

hybrid mauve
#

was it a recent one of yours?

orchid epoch
#

yes

hybrid mauve
#

was just chatting w/ @neat prairie about having a separate section for "my local traces"

orchid epoch
#

yeah or just "my traces"

#

(but yes)

#

@hybrid mauve related issue: I tried fixing the variable in shell mode, then telling the CLI agent to try again. But it said the error was still there

#

(see the end of the same trace)

neat prairie
#

also: trace pagination is part of the sunset v2 project, so you should be able to find older traces

orchid epoch
#

Oh right that page is still React right?

hybrid mauve
#

there's some other funny looking (and missing) data in your trace, was trying to poke around since we should see changes made to the Env at max verbosity, but the data is missing

#

oh wait, it loaded on refresh