You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Timeout errors currently must return a 200 status to be rendered correctly by the Playground javascript. The javascript needs to be updated to also parse 4xx errors correctly, then the playground should be updated to return responses with a correct code. Currently, unsuccessful requests of any kind are treated the same as a 5xx.
This may have implications for the Tour or other places where the playground is used.
This changes the Playground to stop storing build and run timeout
responses in the cache. These responses could get cached when the
Playground was unhealthy, leaving some trivial snippets to be cached
incorrectly, confusing users.
Adds testing for our caching logic.
Updates golang/go#38546
Updates golang/go#38576
Change-Id: Idd2106d673162d9eea8536fe2433f74c23ed6e8a
Reviewed-on: https://go-review.googlesource.com/c/playground/+/229307
Run-TryBot: Alexander Rakoczy <alex@golang.org>
TryBot-Result: Gobot Gobot <gobot@golang.org>
Reviewed-by: Dmitri Shuralyov <dmitshur@golang.org>
Timeout errors currently must return a 200 status to be rendered correctly by the Playground javascript. The javascript needs to be updated to also parse 4xx errors correctly, then the playground should be updated to return responses with a correct code. Currently, unsuccessful requests of any kind are treated the same as a 5xx.
This may have implications for the Tour or other places where the playground is used.
Related to #38546
The text was updated successfully, but these errors were encountered: