#@vito @juliancr looking at this trace,

1 messages · Page 1 of 1 (latest)

mighty merlin
#

Looks similar to the earlier one, but at the bottom instead of the top?

orchid nova
#

yeah, now that the tree auto-collapses we have a lot more room to play with beneath it, so showing a more abridged error summary seemed like a good way to salvage the old UI (which was way too verbose)

#

it also shows that instead of the logs when there are errors, since when there are errors the logs tend to just be a poorer representation of the same thing. not a perfect heuristic, and there's a bug where it sometimes shows both. just trying things out to improve the error UX

mighty merlin
#

I kind of liked the previous iteration, one tree, just with the errors expanded

orchid nova
#

the main issue was performance; once we get that under control we can try it out again

#

it's a tricky balance, since auto-expanding will also push other errors off-screen

#

so i kind of like the aerial view => deep dive flow more, personally

mighty merlin
#

While I'm at it, I know you're aware, and it's a tough one to solve, but - having canceled calls show up as errors is probably in my top 5 of issues when in a debugging loop

#

In this particular case: