When does visualization decide to display things and when does it give up?

[hubertp]

As part of the investigation into #6766, I started to notice something weird with visualizations on startup.

Assume a simple project with a few nodes like:

If I start the project again but with some network throttling it will show the waiting status on them for some time

and eventually close them

The data eventually arrives but it is obviously slightly slower due to throttling.
Is this expected? If so, why? I assumed that data from LS can arrive at any time.

[farmaazon]

Visualization close themselves when some operation fails. Perhaps attaching timed out?

The console logs should show the problem.

[hubertp]

I think here may be a similar problem: the ACK for attaching visualization finally arrives, but after 10 s IDE give up. Could you check if this is the case?

Also, the web console logs (after showLogs or with --debug option) should probably tell us why we close those visualizations.

Yeap, the timeout is there, on the IDE side.

[farmaazon]

By "on the IDE side" you mean LS sends reply in time, but IDE interprets it only after 10 seconds (like in #6660)?

[hubertp]

By "on the IDE side" you mean LS sends reply in time, but IDE interprets it only after 10 seconds (like in #6660)?

LS sends replies in time, yes. Then messages are either in transit or IDE interprets them after 10 seconds. Yes, like #6660.

[hubertp]

Alternatively, would it be wrong to just not timeout in IDE after 10 seconds on such visualizations and just continue waiting? Especially on startup?

[MichaelMauderer]

I wonder if it alternatively would be possible to revive a visualization if we receive data for it, even if we had already given up on waiting for it.

But waiting longer would make for the better UX I guess.

[farmaazon]

Closing, as both the timeout and better reporting are already reported as issues.