Open rhysyngsun opened 4 months ago
How similar is this to the work @jkachel is doing on https://github.com/mitodl/mit-open/pull/693
@rhysyngsun what does "pushing us well over the 30 second Heroku request timeout." mean?
Heroku has a 30 second request timeout: https://devcenter.heroku.com/articles/request-timeout
This should not be automatically closed. This can be closed once the changes added in https://github.com/mitodl/ol-django/pull/152 are integrated with MITx Online.
Blocked by https://github.com/mitodl/ol-django/pull/156
Even though we made this change, we had another outage. Unlike the first outage, instead of PostHog timing out, it returned an error. So we need to add better error handling.
Description/Context
Posthog had an outage which caused calls to their API to timeout.
We worked around this by setting
IN_TEST_SUITE=True
andFEATURES_DEFAULT=True
because we were fortunate enough to have all features enabled. It took some time to evaluate if this was the correct way to address the issue becauseIN_TEST_SUITE
sounds like it could have other undesirable effects.Plan/Design
IN_TEST_SUITE
toPOSTHOG_ENABLED
default_client
default_client
: https://github.com/PostHog/posthog-python/blob/master/posthog/__init__.py#L441-L455