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
I'm currently deploying a new INGInious server, and run into what I think is a conflict with the werkzeug package version.
INGInious installation details
Version: 0.8.7, installed via pip on a Debian 12 and running on Apache/WSGI
To Reproduce
Steps to reproduce the behavior:
Install INGInious with pip in a venv
Configure Apache WSGI following the INGInious doc
When displaying the main page, the INGInious app gives an error message. In the logs, the following exception shows :
Traceback (most recent call last):
File "/inginious/lib/python3.11/site-packages/flask/app.py", line 904, in finalize_request
response = self.process_response(response)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/inginious/lib/python3.11/site-packages/flask/app.py", line 1284, in process_response
self.session_interface.save_session(self, ctx.session, response)
File "/inginious/lib/python3.11/site-packages/inginious/frontend/flask/mongo_sessions.py", line 143, in save_session
response.set_cookie(self.get_cookie_name(app), session_id,
File "/inginious/lib/python3.11/site-packages/werkzeug/sansio/response.py", line 227, in set_cookie
dump_cookie(
File "/inginious/lib/python3.11/site-packages/werkzeug/http.py", line 1301, in dump_cookie
if not _cookie_no_quote_re.fullmatch(value):
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
TypeError: cannot use a string pattern on a bytes-like object
2024-08-21 20:38:30,215 - inginious.webapp.requests - INFO - 127.0.0.1:46372 - "- GET /" - 500 INTERNAL SERVER ERROR
The same exception occurs while running inginious directly with the inginious-webapp executable.
Temporary Fix
I was able to solve this issue by downgrading Werkzeug to version 2.3.7 instead of 3.0.1. Maybe this is a compatibility issue?
The text was updated successfully, but these errors were encountered:
Hello,
I'm currently deploying a new INGInious server, and run into what I think is a conflict with the werkzeug package version.
INGInious installation details
To Reproduce
Steps to reproduce the behavior:
The same exception occurs while running inginious directly with the inginious-webapp executable.
Temporary Fix
I was able to solve this issue by downgrading Werkzeug to version 2.3.7 instead of 3.0.1. Maybe this is a compatibility issue?
The text was updated successfully, but these errors were encountered: