Project

General

Profile

Actions

Bug #17231

closed

Stuck on loading screen after login

Added by Peter Amstutz over 3 years ago. Updated over 3 years ago.

Status:
Resolved
Priority:
Normal
Assigned To:
Category:
Workbench2
Target version:
Story points:
-
Release relationship:
Auto

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.


Subtasks 1 (0 open1 closed)

Task #17243: ReviewResolvedPeter Amstutz01/13/2021Actions
Actions #1

Updated by Peter Amstutz over 3 years ago

  • Description updated (diff)
  • Subject changed from Sometimes stuck on loading screen after login to Stuck on loading screen after login
Actions #2

Updated by Peter Amstutz over 3 years ago

  • Target version set to 2021-01-06 Sprint
Actions #3

Updated by Peter Amstutz over 3 years ago

  • Assigned To set to Daniel Kutyła
Actions #4

Updated by Daniel Kutyła over 3 years ago

  • Status changed from New to In Progress
Actions #6

Updated by Peter Amstutz over 3 years ago

  • Target version changed from 2021-01-06 Sprint to 2021-01-20 Sprint
Actions #7

Updated by Peter Amstutz over 3 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

Actions #9

Updated by Peter Amstutz over 3 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: #240

Moved the code to other lifecycle method

This LGTM

Actions #10

Updated by Daniel Kutyła over 3 years ago

  • Status changed from In Progress to Resolved
Actions

Also available in: Atom PDF