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
The Playground mistakenly caches Timeout errors during builds or running of snippets. This is confusing to users if their build has timed out due to some instability. Some trivial play snippets that should have never timed out are now cached.
The (*server).commandHandler() function needs to be updated, as well as purging our existing cache.
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 <[email protected]>
TryBot-Result: Gobot Gobot <[email protected]>
Reviewed-by: Dmitri Shuralyov <[email protected]>
The Playground mistakenly caches Timeout errors during builds or running of snippets. This is confusing to users if their build has timed out due to some instability. Some trivial play snippets that should have never timed out are now cached.
The
(*server).commandHandler()
function needs to be updated, as well as purging our existing cache./cc @bcmills @gus @dmitshur
The text was updated successfully, but these errors were encountered: