Trace progress bar shows different status when collapsed vs. open

[Jsyvanen-algo]

Description

When viewing trace timelines in a collapsed state, many requests seem to be ongoing and running for a very long time. When toggled open to show spans, timeline updates and request appears completed. When collapsed again timeline reverts to ongoing state.

Below are screenshots of a trace in open vs. closed state. The top timeline should match but appear as 6.87s vs. 189s

Open:

Closed:

Python, Logfire & OS Versions, related packages (not required)

[alexmojaki]

does this go away when you refresh the page?

[Jsyvanen-algo]

does this go away when you refresh the page?

@alexmojaki No unfortunately not. In these cases I noticed that a 200 response code has come back from server but the progress bar still on going (unless you expand to the span view).

[alexmojaki]

Can you email a public trace or a project invite to engineering@pydantic.dev?

[Jsyvanen-algo]

If I search historical traces with SQL the progress bar always appears finished and the request time corrects itself. The issue is on live view. I'll try to capture some live ones soon.

[Jsyvanen-algo]

@petyosi @alexmojaki this is really hard to share via a public trace since the GUI considers it a "pending" trace in the top level view and blocks public trace sharing. As soon as the spans are expanded and the GUI realises the request is actually completed the correct timeline for the trace comes into view and you can't get the "Ongoing" state back.

Would a video help? Or a call? How can I further help? We'd really like this resolved.

[petyosi]

@Jsyvanen-algo I send you a direct message in the Logfire Slack. When convenient, let's have a huddle there.