Bug #16475

Javascript mystery investigation on WB2 workaround

Added by Lucas Di Pentima 4 months ago. Updated about 2 months ago.

Status:
Resolved
Priority:
Low
Assigned To:
-
Category:
-
Target version:
Start date:
Due date:
% Done:

0%

Estimated time:
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

Related to Arvados - Feature #15881: [controller] LDAP login supportResolved05/06/2020

History

#1 Updated by Lucas Di Pentima 4 months ago

#2 Updated by Lucas Di Pentima 4 months ago

  • Target version changed from 2020-06-03 Sprint to 2020-06-17 Sprint

#3 Updated by Peter Amstutz 4 months ago

  • Target version changed from 2020-06-17 Sprint to 2020-07-01 Sprint

#4 Updated by Lucas Di Pentima 3 months ago

  • Target version changed from 2020-07-01 Sprint to 2020-07-15

#5 Updated by Lucas Di Pentima 3 months ago

  • Target version changed from 2020-07-15 to 2020-08-12 Sprint

#6 Updated by Peter Amstutz 3 months ago

  • Assigned To changed from Lucas Di Pentima to Daniel Kutyła

#7 Updated by Daniel Kutyła 2 months ago

  • Status changed from New to In Progress

#8 Updated by Peter Amstutz about 2 months ago

  • Priority changed from Normal to Low
  • Assigned To deleted (Daniel Kutyła)
  • Status changed from In Progress to Resolved
  • Category deleted (Workbench2)

#9 Updated by Peter Amstutz about 2 months ago

Conclusion was it was just confusion about order-of-operations and lack of parenthesis to group it properly.

Also available in: Atom PDF