search

zeeguu / web

Frontend for the zeeguu web application.
https://www.zeeguu.org
5 stars 9 forks source link

calling get_plain_text on the /language_preferences page? #434

Open mircealungu opened 3 months ago

mircealungu commented 3 months ago
image

on the API backend I see: 

[Tue Jul 30 21:29:27.910444 2024] [wsgi:error] [pid 22:tid 139647092348608] [remote 172.19.0.1:58956] Traceback (most recent call last):
[Tue Jul 30 21:29:27.910823 2024] [wsgi:error] [pid 22:tid 139647092348608] [remote 172.19.0.1:58956]   File "/Zeeguu-API/zeeguu/api/utils/route_wrappers.py", line 45, in wrapped_view
[Tue Jul 30 21:29:27.910866 2024] [wsgi:error] [pid 22:tid 139647092348608] [remote 172.19.0.1:58956]     flask.abort(401)
[Tue Jul 30 21:29:27.910920 2024] [wsgi:error] [pid 22:tid 139647092348608] [remote 172.19.0.1:58956]   File "/usr/local/lib/python3.12/site-packages/flask/helpers.py", line 277, in abort
[Tue Jul 30 21:29:27.910930 2024] [wsgi:error] [pid 22:tid 139647092348608] [remote 172.19.0.1:58956]     current_app.aborter(code, *args, **kwargs)
[Tue Jul 30 21:29:27.910964 2024] [wsgi:error] [pid 22:tid 139647092348608] [remote 172.19.0.1:58956]   File "/usr/local/lib/python3.12/site-packages/werkzeug/exceptions.py", line 863, in __call__
[Tue Jul 30 21:29:27.910971 2024] [wsgi:error] [pid 22:tid 139647092348608] [remote 172.19.0.1:58956]     raise self.mapping[code](*args, **kwargs)
[Tue Jul 30 21:29:27.911006 2024] [wsgi:error] [pid 22:tid 139647092348608] [remote 172.19.0.1:58956] werkzeug.exceptions.Unauthorized: 401 Unauthorized: The server could not verify that you are authorized to access the URL requested. You either supplied the wrong credentials (e.g. a bad password), or your browser doesn't understand how to supply the credentials required.
igawaclawska commented 3 months ago

It seems like something that might be related to the user session creation, but I will need to investigate it further on 15.08 to find the cause.

igawaclawska commented 2 months ago

@mircealungu , @tfnribeiro - I'm currently looking at it, and I'm not getting these errors/exception messages either in prod or in dev. My consoles look as below. Does it still happen on your end?

Screenshot 2024-08-29 at 11 53 44 Screenshot 2024-08-29 at 11 54 34

Also, like Tiago, I suspect It is similar to issue #435, which is fixed now. I think that fix addressed this issue as well - this is why I no longer see those console messages.