-
Notifications
You must be signed in to change notification settings - Fork 17.8k
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
x/talks: go Present hosted on go-talks returning 403 api.github.com error #58906
Comments
CC @golang/release |
cc @golang/tools-team |
This comment was marked as duplicate.
This comment was marked as duplicate.
hello, this hangs for a while now and is still broken - can you please provide some information what's the reason behind? |
I haven't taken a look at the source code, but would this be something one could just hosted on Vercel/Linode/etc? All my presentations are in |
I'm facing the same issue as well. Older talks seems to load properly since they are probably cached. This seems to be an ongoing issue for a while, there are many people that rely on https://go-talks.appspot.com to present their talks. If the Go team is not planning on continuing to support it properly, maybe that should be stated or marked discontinued. I do appreciate all the work put into this tool, it has served us well over the years and I would love for it to continue to work properly. cc @golang/release |
@golang/tools-team are there any plans to fix this? |
What version of Go are you using (
go version
)?Does this issue reproduce with the latest release?
Yes
What operating system and processor architecture are you using (
go env
)?go env
OutputWhat did you do?
Have a public repo using the Go Present package. Earlier today was able to access this presentation via https://go-talks.appspot.com/github.com/lhogan3/GoPresentation/slides/gopres.slide#1 but now getting a 403 error from api.github.com saying that it is not able to access this resource.
What did you expect to see?
My presentation able to be navigated.
What did you see instead?
An error screen saying that there was a 403 error.
The text was updated successfully, but these errors were encountered: