-
Notifications
You must be signed in to change notification settings - Fork 212
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
"Run" doesn't run the program, no build result or output appears #955
Comments
I can occasionally get an error message:
|
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:
|
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:
If something could be done about this, it'd be appreciated. |
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.
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). |
What lack of garbage collection does to an individual |
This is happening again now |
Got this message today: 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 Interesting: if I choose 'Nighty' builds instead of 'Stable', it works after extremely long processing (about 25 seconds for an extremely small and simple code of 10 lines (input of 2 strings -> convertation to u16 -> pure mathematical calculation -> print) |
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.
The text was updated successfully, but these errors were encountered: