-
Notifications
You must be signed in to change notification settings - Fork 441
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
LocaleInterceptor blocks new request #819
Comments
Thanks for reporting this @atarix83 ! This does sound like an obvious bug we need fixing, and also sounds related to #739. For now I've added to the beta4 Todo list. @artlowel : Any thoughts on whether we should solve this issue separately? Or would you rather we bundle this as part of your current work on #739? |
The way @atarix83 describes it, it should go away if the caching issue is fixed. But in general, blocking the entire app because we can't get the eperson language seems problematic. It would probably be good to have a fix on the side of the interceptor as well: where if the eperson is undefined, we don't include the eperson language in the request, rather than blocking the request. |
@artlowel I agree, but the issue is on getAuthenticatedUserFromStore method that doesn't emit a value due to |
@atarix83 after looking at it closer, I don't see a way to deal with the fact that the first payload will always be undefined either. Perhaps just leave out the eperson language until the cache is fixed. |
Describe the bug
The new LocaleInterceptor blocks every new rest request when it can't retrieve the logged eperson object because the related entry cache object is expired. This is made in the LocaleService and was due a bug reported in this issue. The severe consequence is that the application is blocked after this error occurs.
A temporary workaround, until cache issuea are fixed, is to disabled that part of the code
The text was updated successfully, but these errors were encountered: