summaryrefslogtreecommitdiff
path: root/docs/admin/settings/settings_engines.rst
diff options
context:
space:
mode:
authorMarkus Heiser <markus.heiser@darmarIT.de>2025-07-08 13:46:39 +0200
committerGitHub <noreply@github.com>2025-07-08 13:46:39 +0200
commitbd593d0bad2189f57657bbcfa2c5e86f795c680e (patch)
tree36fcd14067d923a5c90d49f068ef54e5b275d74c /docs/admin/settings/settings_engines.rst
parentfe52290e653e969c959b3160c1a09f02e751efd2 (diff)
[fix] granian: enabling debug on searxng-docker causes server crash (#4985)
When debugging is enabled, the context in which the process is running (uWSGI or `Flask.run` server) was previously checked [1]. This check has not yet taken the granian server into account. ---- The check is actually only required for the developer environment (`make run`) [2] and is intended to prevent double loading of modules when initializing a Flask server [3]. In the long term, we should find a more robust solution that explicitly enables the specific features of a development environment via switches. Further information on this problematic code can be found in [4][5][6]. [1] https://github.com/searxng/searxng/issues/4973#issuecomment-3047890957 [2] https://flask.palletsprojects.com/en/stable/api/#flask.Flask.run [3] https://github.com/pallets/flask/issues/5307#issuecomment-1774646119 [4] https://github.com/searxng/searxng/pull/1656#issuecomment-1214198941 [5] https://github.com/searxng/searxng/pull/1616#issuecomment-1206137468 [6] https://stackoverflow.com/a/25504196 - closes: https://github.com/searxng/searxng/issues/4973 Signed-off-by: Markus Heiser <markus.heiser@darmarit.de>
Diffstat (limited to 'docs/admin/settings/settings_engines.rst')
0 files changed, 0 insertions, 0 deletions