-
Notifications
You must be signed in to change notification settings - Fork 17.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
tour: translators must update their tools repo and re-deploy #15693
Comments
The various sites need to re-deploy using the updated version of the tools repository (any version after revision f3109af). |
Here are the sites that need to be / have been updated:
The maintainers may fix this by running |
An aside: I'll use this occasion to collect the details of the maintainers of these translated tours, so that it is easier to contact them in the future. |
The translation for go-tour-id2.appspot.com has been re-deployed. Thank you for replying. But I am still can not figure out how to make the code can Run in local |
@shuLhan there's some bug in the urlfetch implementation of |
Italian version just re-deployed 😎 |
@alebaffa grazie! |
tour: German don't work |
@michivo thank you! |
All the tours except the one on https://go-tour-uz.appspot.com/ have been re-deployed, and this issue is >12 months old, so I think this can be closed. |
I maintain the tour translation for Bahasa Indonesia. One of user reported that none of the example code can or display any output after clicking Run button. I check it online for our local tour and he was right. So, I check another local tour (Brazil and France, picked randomly) and none of them can run example or print any output too.
I check with the local version using
goapp serve
, with following information,What version of Go are you using (
go version
)?What operating system and processor architecture are you using (
go env
)?What did you do?
goapp serve
on local tour repositoryWhat did you expect to see?
The code will output,
What did you see instead?
From the goapp serve log,
The text was updated successfully, but these errors were encountered: