commit | cb3741f468aa1d6e77078cb6c38b8fa762713634 | [log] [tgz] |
---|---|---|
author | Alexander Rakoczy <alex@golang.org> | Fri Apr 03 16:03:56 2020 -0400 |
committer | Alexander Rakoczy <alex@golang.org> | Wed Apr 08 21:16:28 2020 +0000 |
tree | e646ab5ea4cfd66cd0e5b9abebd869980460ceb1 | |
parent | 15e968511d3060ae3d38f53ab43cc48529d26825 [diff] |
playground: use the correct contexts for sandbox requests The sandbox code was incorrectly using the request context instead of the build context when trying to determine if there was a DeadlineExceeded error. This would manifest to the user as a blank response in the build output, rather than the correct error. Additionally, the sandbox code was using the incorrect context for running the binary. This means we were not correctly enforcing maxRunTime. Finally, tests do not pass with a maxRunTime of 2 seconds on my machine, and it's unclear what impact enforcing this would have on production code. I've increased it to 5 seconds. It would be prudent to add metrics here to determine how user programs are impacted in a follow-up issue. Updates golang/go#25224 Updates golang/go#38052 Change-Id: I59aa8caeb63a9eec687bfbe4f69c57f71a13440d Reviewed-on: https://go-review.googlesource.com/c/playground/+/227350 Reviewed-by: Andrew Bonventre <andybons@golang.org> Reviewed-by: Bryan C. Mills <bcmills@google.com>
This subrepository holds the source for the Go playground: https://play.golang.org/
# build the image docker build -t playground .
docker run --name=play --rm -p 8080:8080 golang/playground & # run some Go code cat /path/to/code.go | go run client.go | curl -s --upload-file - localhost:8080/compile
Playground releases automatically triggered when new Go repository tags are pushed to GitHub, or when master is pushed on the playground repository.
For details, see deploy/go_trigger.json, deploy/playground_trigger.json, and deploy/deploy.json.
After making changes to trigger configuration, update configuration by running the following Make target:
make update-cloudbuild-trigger
The Cloud Build configuration will always build and deploy with the latest supported release of Go.
gcloud builds submit --config deploy/deploy.json .
Building the playground Docker container takes more than the default 10 minute time limit of cloud build, so increase its timeout first (note, app/cloud_build_timeout
is a global configuration value):
gcloud config set app/cloud_build_timeout 1200 # 20 mins
Alternatively, to avoid Cloud Build and build locally:
make docker docker tag golang/playground:latest gcr.io/golang-org/playground:latest docker push gcr.io/golang-org/playground:latest gcloud --project=golang-org --account=you@google.com app deploy app.yaml --image-url=gcr.io/golang-org/playground:latest
Then:
gcloud --project=golang-org --account=you@google.com app deploy app.yaml
To submit changes to this repository, see https://golang.org/doc/contribute.html.