-
Notifications
You must be signed in to change notification settings - Fork 13
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
In some cases, barista loses group information after refresh (group dropdown / selection not available after login) #569
Comments
Wow, that's weird. I can duplicate. |
Refreshing has no effect (not that it should). |
Possibly a supervisord restart attempt tried to bring up another barista, clobbering or making the running one unhappy?
|
Interesting that it was the local vantage server reporting there. |
@BarbaraCzub I seem to have it working again. That was a little odd. |
Note that barista was reset, removing all current sessions and resetting temporary position information. |
Thank you for fixing this @kltm . The group selection option is back now. However, would it be possible to change my default 'assigned by' field to 'ARUK-UCL'? ( cc @RLovering ) |
I think it has to do with the order in which your groups are listed in the users.yaml file. I dont know if something else needs to happen; can you please test again ? Thanks, Pascale |
Hi Pascale, 'BHF-UCL' is still displayed as my default 'assigned by' option. |
So, while I'm working on a model, even if I select 'ARUK-UCL' to start with, if I need to refresh the page, it always reverts back to 'BHF-UCL'. |
Did you try logging out and log back in ? |
I have now. 'BHF-UCL' is still the default option. |
Maybe it could be removed completely from next to my name in the users.yaml file? |
Sure - but still the order should be taken into account. I'd like to know what the issue is; perhaps this is not immediate. |
No, it's not immediate. |
I'll put in to do the services restart later today. |
Thanks @kltm I'll check tomorrow whether my default group has been updated. (Unless 'services restart' is referring to something else?). |
Thanks @kltm. My default group has now been updated. |
When I was making GO-CAM models, which I refer to in this annotation ticket geneontology/go-annotation#2047, I was not able to select the ARUK-UCL attribution (or any other attribution). The drop-down menu with this option seems to have disappeared. So now all of the models appear to be assigned by GO_Noctua (instead of ARUK-UCL).
cc @RLovering
Here are the model details:
The text was updated successfully, but these errors were encountered: