-
Notifications
You must be signed in to change notification settings - Fork 2
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
test: Simulate outages #514
Conversation
@razor-x I keep getting 401 errors in CI. Is this an issue on my end? |
It may be something with the react query cache, it's possible if there is an error the behavior is to keep the latest data. Is there a way to reset the cache when switching the global arg? Actually, this may be a more general issue I posted here where cache is not reset when auth changes: #462 Might be more serious then I originally thought. |
@razor-x Yeah, probably the cache. We can manually reset it either via the Is this cache clearing logic something we'd like to add to our primary provider or do we want to encapsulate it within Storybook (if possible)? In any case, is this a blocker for this PR? |
Have absolutely no clue why/how this was modified....
Not a blocker for this. |
Adds the ability to simulate outages by toggling between publishable keys.
Note: Going from
Normal
toOutage
sometimes requires a reload. Any ideas on how we can eliminate this?