You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Came across this again. Since the button clears the caches on the server, this action currently considered “administration” of the dataset, not “read”. We could now
(1) Allow this for any user, since it cannot do much harm, except cause extra load and decrease perf for all
(2) Soften the behavior of the button in the front-end, if the user does not have administration right for the dataset, to only reload the data from the backend, but not call the clear-caches route
(3) Hide the button entirely if the user does not have administration rights for the dataset
Hm, initially, I was about to say (2), but I'm not really sure what the use case for unauthorized users is in general. They probably didn't change the dataset on the server. Therefore, (3) seems reasonable to me.
Alternatively, one could do (1) and combine it with a back-end sleep of a few seconds to do some cheapo rate limiting. However, I still don't really see a good use case for unregistered users. So, let's do (3) if nobody disagrees.
Expected Behavior
Probably, the button shouldn't be available for non-authorized users.
Current Behavior
It fails with unhelpful error messages.
Steps to Reproduce the bug
I was clicking the "reload" button on the color layer in this dataset: https://webknossos.org/datasets/scalable_minds/l4dense_motta_et_al_demo/view
The text was updated successfully, but these errors were encountered: