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
{{ message }}
This repository has been archived by the owner on Jul 26, 2024. It is now read-only.
When we're rolling out a new deploy, the caches need to be filled. This can result in a spike of 500 errors to the client, which can cause a mild panic attack with Ops.
We should consider options to either return a softer error type (206?), an empty result, trigger a lag so that values are eventually filled and returned, or some other kinder behavior.
┆Issue is synchronized with this Jira Task
┆epic: Contile production v1
The text was updated successfully, but these errors were encountered:
#337)
NOTE:
this changes the behavior of the `CONTILE_TEST_MODE` flag to be one of
several states:
**TestFakeResponse** = return a fake response from the ADM server
(previous "true")
**TestTimeout** = "timeout" a request to the ADM server.
Closes#336
When we're rolling out a new deploy, the caches need to be filled. This can result in a spike of 500 errors to the client, which can cause a mild panic attack with Ops.
We should consider options to either return a softer error type (206?), an empty result, trigger a lag so that values are eventually filled and returned, or some other kinder behavior.
┆Issue is synchronized with this Jira Task
┆epic: Contile production v1
The text was updated successfully, but these errors were encountered: