Project Configuration - Run Prebuild always shows "Connecting to workspace Logs..."

[jldec]

This is possibly a duplicate of #5573

Successful prebuilds should either show a log, or a message that there was no stdout.

Users are confused by the message "Connecting to workspace logs..." which persists even if the prebuild succeeds.

[geropl]

@jldec Also, possibly related to #5904: I'm not sure we report "RUNNING"/"READY" correctly atm.

[mikenikles]

I notice that with https://gitpod.io/projects/openvscode-server/c1cbd150-40e3-4d26-a1fd-545e09d1e20b today. The UI shows the Prebuild status as RUNNING, 18 minutes and counting, but all I see is Connecting to workspace logs.

[jldec]

Scheduled.
The inconsistent behavior of prebuild status and logs is adding to the perception of prebuild unreliability.

[jankeromnes]

"Connecting to workspace logs..." was a pure front-end thing, which got removed in #8558:

Don't always print 'Connecting to workspace logs...' (it's somewhat misleading)

Context: We initially added it to show the user that the front-end is loaded, and now the backend is working to fetch what the user wants. However, we've observed that the backend is unreliable, and can fail in various different stages, so it's not always actually connecting (e.g. sometimes there is no workspace to connect to, other times it cannot find the logs for some reason).

Maybe showing a blank logs view is better than a somewhat misleading message.

A better, long-term fix would be to implement the Headless Logs (again) RFC, i.e. "central log ingestion service to content-service, make supervisor a writing client to this service".