Actions
Bug #16475
closed
Javascript mystery investigation on WB2 workaround
Story points:
-
Description
On #15881, when adding code for the LDAP login option, we had to do a workaround because of a logic misbehavior, explained on https://dev.arvados.org/issues/15881#note-27
Investigate the real cause of the failure as javascript is single threaded so the reevaluation of state.auth.remoteHostsConfig[state.auth.loginCluster || state.auth.homeCluster] should always return the same value.
Related issues
Updated by Lucas Di Pentima almost 4 years ago
- Related to Feature #15881: [controller] LDAP login support added
Updated by Lucas Di Pentima almost 4 years ago
- Target version changed from 2020-06-03 Sprint to 2020-06-17 Sprint
Updated by Peter Amstutz almost 4 years ago
- Target version changed from 2020-06-17 Sprint to 2020-07-01 Sprint
Updated by Lucas Di Pentima almost 4 years ago
- Target version changed from 2020-07-01 Sprint to 2020-07-15
Updated by Lucas Di Pentima almost 4 years ago
- Target version changed from 2020-07-15 to 2020-08-12 Sprint
Updated by Peter Amstutz almost 4 years ago
- Assigned To changed from Lucas Di Pentima to Daniel Kutyła
Updated by Daniel Kutyła almost 4 years ago
- Status changed from New to In Progress
Updated by Peter Amstutz almost 4 years ago
- Priority changed from Normal to Low
- Assigned To deleted (
Daniel Kutyła) - Status changed from In Progress to Resolved
- Category deleted (
Workbench2)
Updated by Peter Amstutz almost 4 years ago
Conclusion was it was just confusion about order-of-operations and lack of parenthesis to group it properly.
Actions