-
Notifications
You must be signed in to change notification settings - Fork 12.7k
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
use playpen to implement a sandbox for running code on the rust website #6916
Comments
👍 |
(bug triage) Still a great idea; not a blocker. |
TheHydroImpulse/rust-website seems to implement that. |
@adridu59 Yeah, I've been implementing @thestinger's playpen for the website. |
We've got an ec2 instance running now at ec2-54-215-67-200.us-west-1.compute.amazonaws.com. There's still a number of tasks to take care of before turning this on officially, and I'd love to see them get done! I've added a number of TODO items to the issue description. |
This is now (temporarily) available at http://playtest.rust-lang.org. |
Sweet!
|
A CNAME has been setup, this is now available at http://play.rust-lang.org/. I'm going to close this issue in favor of more specific ones like #14575. Thanks @thestinger, awesome work! |
…arth Don't re-export `clippy_utils::diagnostics::*` changelog: none Continues rust-lang#6907
I made a simple sandbox for the bot on #rust, and I plan on making a web frontend for it. The service as a whole could run in a VM since it's still vulnerable to a kernel exploit in one of the whitelisted system calls.
Since
rustc
uses at least 70MiB of memory and up to 128-150MiB for reasonably small examples, we'll need to limit the concurrency based on the chosen resource limit for the sandbox and the memory available.This would be a nice way to let people try to language before going through the relatively long compile.
TODO list
play.rust-lang.org
(or some similar name)The text was updated successfully, but these errors were encountered: