Bug #17231
closedStuck on loading screen after login
Description
I don't know if this happens every time or just sometimes, but after logging in, I get stuck at a screen with a spinner and the app never loads. The workaround is to reload the page.
Updated by Peter Amstutz almost 4 years ago
- Description updated (diff)
- Subject changed from Sometimes stuck on loading screen after login to Stuck on loading screen after login
Updated by Peter Amstutz almost 4 years ago
- Target version set to 2021-01-06 Sprint
Updated by Daniel Kutyła almost 4 years ago
- Status changed from New to In Progress
Updated by Daniel Kutyła almost 4 years ago
New version first commit: https://dev.arvados.org/projects/arvados-workbench-2/repository/revisions/685165ce25015be034d92456513785abe03e9ba0
Test run: developer-tests-workbench2: #224
Replaced the way we change page url
Updated by Peter Amstutz almost 4 years ago
- Target version changed from 2021-01-06 Sprint to 2021-01-20 Sprint
Updated by Peter Amstutz almost 4 years ago
From chat:
from what I see when this replace action is triggered there is no user data within the store
that is why I am saying that store is not ready
yea I see. the redirect is chained after saveApiToken() but if you look at saveApiToken() it looks like the getUserDetails promise is what gets returned
so the the INIT_USER action and the redirect action get dispatched at the same time
so, I think we want to return a promise from saveApiToken() that calls back after INIT_USER
like, the timeout trick works, but it's a hack, we should sequence the callbacks correctly
Updated by Daniel Kutyła almost 4 years ago
New version first commit: https://dev.arvados.org/projects/arvados-workbench-2/repository/revisions/f657dca6334ce910559100ba99666a95cfbc7236
Test run: developer-tests-workbench2: #240
Moved the code to other lifecycle method
Updated by Peter Amstutz almost 4 years ago
Daniel Kutyła wrote:
New version first commit: https://dev.arvados.org/projects/arvados-workbench-2/repository/revisions/f657dca6334ce910559100ba99666a95cfbc7236
Test run: developer-tests-workbench2: #240Moved the code to other lifecycle method
This LGTM
Updated by Daniel Kutyła almost 4 years ago
- Status changed from In Progress to Resolved
Applied in changeset arvados-workbench2|df6ddb0c91aaed31cd242b5250835fce4308ef9f.