-
Notifications
You must be signed in to change notification settings - Fork 4.4k
UI Bug fix: Fix DR Secondary view #31478
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
Conversation
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
CI Results: |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Just a clean up of this file. No tests were removed. And the only test added was to check that the analytics service is run on a dr primary (so the opposite test of what we check for on the dr secondary).
Build Results: |
* test coverage and the fix * not working * fix failing test * fix another test * changelog * the correct changelog number
* UI Bug fix: Fix DR Secondary view (#31478) * test coverage and the fix * not working * fix failing test * fix another test * changelog * the correct changelog number * selector backporting things
Description
The DR secondary view failed to load after PR #30425. The error occurred because of the addition of the
async
keyword to theafterModel
hook. My best guess as to why this breaks the DR Secondary transition is thatasync
causes Ember to wait for any awaited promises before completing the route transition. For most routes, this is fine, but DR secondary is sensitive to timing, and the transition hangs/fails silently, breaking the transition.Note: The addition of
async
on theafterModel
hook does not cause a failure for Performance Secondaries.To repro:
d7bb0adfe0
(the commit right before the Posthog PR), create a DR secondary, and navigate to the UI view. Then, check out the Posthog commit689ede2da5
and follow the same steps. It works on the commit before, and fails on the regression commit.async
before theafterModel
hook on the cluster route, and the DR secondary will fail to transition. Removeasync
, and it will transition. This shows that it's not thethis.analytics
service check that's breaking the flow, it's theasync
keyword added to theafterModel
hook.Failure:

After fix:
