rust-playground
rust-playground copied to clipboard
"Run" doesn't run the program, no build result or output appears
Just opening the playground in a blank profile and hitting "Run" leads to... basically nothing: the output pane appears on the right-hand side of the screen, but it just says "Execution" and "Standard error", without actually showing the output of the compiler or running the program.
I can occasionally get an error message:
docker: Error response from daemon: mkdir /var/lib/docker/overlay2/6e37d4663a1c93dced3accc4830032c7b94591072c4a9a083d327c05efc2c267-init: no space left on device.
See 'docker run --help'.
Disk space appears to have gone to zero which isn't good. Restarted the server and got some back. Root cause not clear.
@shepmaster it seems like it happened again
It's still happening.
New error this time:
The server reported an error: Unable to process the execute request: Could not start the container: Unable to load original Cargo.toml: Could not read the file: Did not receive a response from the demultiplexer: channel closed
Sadly...
Disk space appears to have gone to zero which isn't good. Restarted the docker service and got some back. Root cause not clear.
Happened again.
Hi, this appears to be happening for me on https://play.rust-lang.org/. When I hit "Run", nothing shows up. I even checked the Developer Tools, and there's simply no response through the websocket.
Normally, I'd use https://play.integer32.com/ while waiting for the rust-lang one to be fixed, but it's also having issues - when I hit "Run", I'm greeted with this message in the output:
Unable to perform a streaming execute: Could not begin the execution session: Could not start the container: Unable to load original Cargo.toml: Could not read the file: Did not receive a response from the demultiplexer: channel closed
If something could be done about this, it'd be appreciated.
Hi, this appears to be happening for me on https://play.rust-lang.org/. When I hit "Run", nothing shows up. I even checked the Developer Tools, and there's simply no response through the websocket.
An interesting mitigation would be to at least show a client-side timeout / error message when nothing happens. As-is there's just no output so people who just want to "Build" the code and are not careful (so don't notice that the progress / stderr / stdout are missing) might think their program compiled fine. Pretty sure there's been one of those today on /r/rust as they gave a snippet they claimed compiles, even though it does not, and that was around the time the playground was down.
Normally, I'd use https://play.integer32.com/ while waiting for the rust-lang one to be fixed, but it's also having issues - when I hit "Run", I'm greeted with this message in the output:
You can use godbolt as an alternative fallback, though it's a bit less convenient (it might not default to rust, generally defaults to compilation rather than running, and community libraries are generally missing from the latest few compiler revisions).
Disk space appears to have gone to zero
What lack of garbage collection does to an individual
This is happening again now