rust-lang / rust-lang/rust-playground
SIGKILL on code that doesn't compile and doesn't crash the compiler
Open
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 1.4k
- Forks
- 267
- Avg merge
- 3h 2m
- Merged PRs (30d)
- 6
Description
Right now, https://play.rust-lang.org/?version=stable&mode=debug&edition=2018&gist=0c742b14419b5ebe0396bcbd1d72c886 gives me
/playground/tools/entrypoint.sh: line 11: 7 Killed timeout --signal=KILL ${timeout} "$@"
when I try to run it.
I tried again just now and it works again. Maybe the server was overloaded or something?
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Reproduce the provided Playground link and inspect /playground/tools/entrypoint.sh around line 11, including the timeout invocation. Done means establishing whether the SIGKILL comes from the submitted program, timeout or resource handling, or transient server load, with a repeatable test or clear operational finding.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- infrastructure
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100