Skip to content
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

Proofreading gets stuck with expired token #7546

Closed
fm3 opened this issue Jan 11, 2024 · 0 comments · Fixed by #7598
Closed

Proofreading gets stuck with expired token #7546

fm3 opened this issue Jan 11, 2024 · 0 comments · Fixed by #7598

Comments

@fm3
Copy link
Member

fm3 commented Jan 11, 2024

A proofreading (aka editable mapping) annotation could not load anymore (showed missing buckets for all buckets in the header)

Backend logging shows:

2024-01-11 12:40:00,032 [ERROR] com.scalableminds.webknossos.datastore.rpc.RPCRequest - Unsuccessful WS request to https://<datastoreUri>/data/datasets/<orga>/<dataset>/layers/segmentation/data (ID: 269392).Status: 403. Response: Token may be expired, consider reloading. Access forbidden: No read access on dataset

Showed like this for multiple users (not a frontend cache problem)

Restarting webknossos (tracingstore + wk backend container) helped (did not restart the datastore)

Probably a caching issue (?) Unfortunately I don’t have steps to reproduce, seems to occur very rarely.

We should check if the token value should have shown in the logging. Was there no token passed at all?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant