Timeouts cause Playground Communication: Cannot read properties of undefined (reading 'trim')

[mgeisler]

If a Playground program times out (typically due to an infinite loop), we see a strange error message:

Playground Communication: Cannot read properties of undefined (reading 'trim')

We should see if we can handle this better.

[mgeisler]

@Alx-Lai, would you be interested in trying to improve this?

[Alx-Lai]

Sure! I can take a look tomorrow

[Alx-Lai]

The behavior in 1. https://play.rust-lang.org/ vs 2. comprehensive-rust with following program.

fn main() {
    loop {}
}

1. https://play.rust-lang.org/
   There's a textbox showing over runtime.
   

2. comprehensive-rust

Playground Communication: Cannot read properties of undefined (reading 'trim')

[mgeisler]

Hey @Alx-Lai, thanks for testing this so nicely!

I've noticed that the official Playground uses a WebSocket based system now — and the endpoint we use is a simpler one-shot approach. I would like to see us migrate to the WebSocket eventually, but for now, I think we should just wrap the code in a bit of error handling to avoid showing the ugly Cannot read properties of undefined (reading 'trim') message.