Arvados

14841-link-workbench1 @ commit:ff8e417f63a58fb1a44ab89ce3c93d1a91828619

Add link to workbench v1

Add a reducer that holds discovery document config, to read workbenchURL & for future things that need cluster config.

Projects, collections and "processes" are routed to equivalent page on wb1, rest are sent to entry page.

Currently getting an error when clicking the link (https://workbench.c97qk.arvadosapi.com/projects/9tee4-tpzed-dwg8zzn53khc6ij)

 undefined method `uuid' for nil:NilClass.

Are there some things I need to do in order to test this properly?

Also, it might be worth adding a config-reducer test.

Eric Biagiotti wrote:

Currently getting an error when clicking the link (https://workbench.c97qk.arvadosapi.com/projects/9tee4-tpzed-dwg8zzn53khc6ij)

[...]

I think that is a workbench bug, but you're running into it because you are not logged in. Now it passes the api_token along so you will be logged into the same account with the same credentials.

Are there some things I need to do in order to test this properly?

Also, it might be worth adding a config-reducer test.

It is so simple, I'm not really sure what to test.

14841-link-workbench1 @ c74d94dabd5f66bc948f9a9ed6283cdb59fb392b

Peter Amstutz wrote:

Eric Biagiotti wrote:

Currently getting an error when clicking the link (https://workbench.c97qk.arvadosapi.com/projects/9tee4-tpzed-dwg8zzn53khc6ij)

[...]

I think that is a workbench bug, but you're running into it because you are not logged in. Now it passes the api_token along so you will be logged into the same account with the same credentials.

The link to wb1 now acknowledges that I am logged but gives me an inactive account notification. If this is a separate issue, then this story LGTM.

Eric Biagiotti wrote:

Peter Amstutz wrote:

Eric Biagiotti wrote:

Currently getting an error when clicking the link (https://workbench.c97qk.arvadosapi.com/projects/9tee4-tpzed-dwg8zzn53khc6ij)

[...]

I think that is a workbench bug, but you're running into it because you are not logged in. Now it passes the api_token along so you will be logged into the same account with the same credentials.

The link to wb1 now acknowledges that I am logged but gives me an inactive account notification. If this is a separate issue, then this story LGTM.

It looks like you logged in as a federated user (from 9tee4) to c97qk, and the federated user is inactive on c97qk. This might actually be a workbench2 bug, because if you are inactive, you can't really do anything, and the workbench2 UI should tell you that. I'll investigate.

14841-link-workbench1 @ e677489047822fed2dcd48d904ccc46fae5b1615

• Adds inactive user mode
• Always reload user record on page initialization, so we don't use stale information (like whether the user is active or not)