diff options
| author | Markus Heiser <markus.heiser@darmarIT.de> | 2026-02-22 14:44:21 +0100 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2026-02-22 14:44:21 +0100 |
| commit | 191818b865b19270c8c38d905141356a6ba01d9a (patch) | |
| tree | b42ba81cc63263258688a124459dd08ecfa84e99 /tests | |
| parent | 5054e69844cbedfa0f5184955d662d944bcd35c1 (diff) | |
[mod] drop SearXNG's checker (#5767)
To date, there is no analysis for the checker that could be evaluated in any
meaningful way.
- https://github.com/searxng/searxng/issues/3407
- https://github.com/searxng/searxng/pull/3312
The checker would need to be completely redesigned, but even then, its
usefulness and the maintenance required for it would be disproportionate.
TBH: In its current form, it is useless and only consumes resources and
causes the engines to be blocked, because these tests (query terms) come
from *hundreds* of instances and could be interpreted as bot attacks.
Related issues: [search.checker](https://github.com/searxng/searxng/issues?q=label%3A%22search.checker%22)
Signed-off-by: Markus Heiser <markus.heiser@darmarit.de>
Diffstat (limited to 'tests')
| -rw-r--r-- | tests/__init__.py | 1 |
1 files changed, 0 insertions, 1 deletions
diff --git a/tests/__init__.py b/tests/__init__.py index 9c176aedf..8b35161d9 100644 --- a/tests/__init__.py +++ b/tests/__init__.py @@ -82,7 +82,6 @@ class SearxTestCase(aiounittest.AsyncTestCase): # - initialize searx.network, searx.metrics, searx.processors and searx.search.checker searx.search.initialize( - enable_checker=True, check_network=True, enable_metrics=searx.get_setting("general.enable_metrics"), # type: ignore ) |