chore(ui): handle trace not being available without exceptions #33427
+18
−6
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The control flow for loading live traces is currently based on exceptions, and it's hard to follow. It's expected that the live trace only becomes available after a couple retries, but the code doesn't reflect that.
This PR adds some handling for 404s so we represent the "trace not yet available" state with 404 responses instead of
errors. It also renames the
counter
state torerender
to make the intent clearer.Console before this change:
Console after this change:
Closes #33339.