2022-01-19 17:25:24 +01:00
|
|
|
# SPDX-License-Identifier: AGPL-3.0-or-later
|
|
|
|
"""This module implements functions needed for the autocompleter.
|
2014-09-13 18:47:28 +02:00
|
|
|
|
2022-01-19 17:25:24 +01:00
|
|
|
"""
|
2023-02-10 13:40:12 +01:00
|
|
|
# pylint: disable=use-dict-literal
|
2014-09-13 18:47:28 +02:00
|
|
|
|
2022-12-04 22:57:22 +01:00
|
|
|
import json
|
2024-07-01 16:45:20 +00:00
|
|
|
import html
|
2024-01-05 18:15:42 +01:00
|
|
|
from urllib.parse import urlencode, quote_plus
|
2020-08-06 17:42:46 +02:00
|
|
|
|
[refactor] typification of SearXNG (initial) / result items (part 1)
Typification of SearXNG
=======================
This patch introduces the typing of the results. The why and how is described
in the documentation, please generate the documentation ..
$ make docs.clean docs.live
and read the following articles in the "Developer documentation":
- result types --> http://0.0.0.0:8000/dev/result_types/index.html
The result types are available from the `searx.result_types` module. The
following have been implemented so far:
- base result type: `searx.result_type.Result`
--> http://0.0.0.0:8000/dev/result_types/base_result.html
- answer results
--> http://0.0.0.0:8000/dev/result_types/answer.html
including the type for translations (inspired by #3925). For all other
types (which still need to be set up in subsequent PRs), template documentation
has been created for the transition period.
Doc of the fields used in Templates
===================================
The template documentation is the basis for the typing and is the first complete
documentation of the results (needed for engine development). It is the
"working paper" (the plan) with which further typifications can be implemented
in subsequent PRs.
- https://github.com/searxng/searxng/issues/357
Answer Templates
================
With the new (sub) types for `Answer`, the templates for the answers have also
been revised, `Translation` are now displayed with collapsible entries (inspired
by #3925).
!en-de dog
Plugins & Answerer
==================
The implementation for `Plugin` and `Answer` has been revised, see
documentation:
- Plugin: http://0.0.0.0:8000/dev/plugins/index.html
- Answerer: http://0.0.0.0:8000/dev/answerers/index.html
With `AnswerStorage` and `AnswerStorage` to manage those items (in follow up
PRs, `ArticleStorage`, `InfoStorage` and .. will be implemented)
Autocomplete
============
The autocompletion had a bug where the results from `Answer` had not been shown
in the past. To test activate autocompletion and try search terms for which we
have answerers
- statistics: type `min 1 2 3` .. in the completion list you should find an
entry like `[de] min(1, 2, 3) = 1`
- random: type `random uuid` .. in the completion list, the first item is a
random UUID
Extended Types
==============
SearXNG extends e.g. the request and response types of flask and httpx, a module
has been set up for type extensions:
- Extended Types
--> http://0.0.0.0:8000/dev/extended_types.html
Unit-Tests
==========
The unit tests have been completely revised. In the previous implementation,
the runtime (the global variables such as `searx.settings`) was not initialized
before each test, so the runtime environment with which a test ran was always
determined by the tests that ran before it. This was also the reason why we
sometimes had to observe non-deterministic errors in the tests in the past:
- https://github.com/searxng/searxng/issues/2988 is one example for the Runtime
issues, with non-deterministic behavior ..
- https://github.com/searxng/searxng/pull/3650
- https://github.com/searxng/searxng/pull/3654
- https://github.com/searxng/searxng/pull/3642#issuecomment-2226884469
- https://github.com/searxng/searxng/pull/3746#issuecomment-2300965005
Why msgspec.Struct
==================
We have already discussed typing based on e.g. `TypeDict` or `dataclass` in the past:
- https://github.com/searxng/searxng/pull/1562/files
- https://gist.github.com/dalf/972eb05e7a9bee161487132a7de244d2
- https://github.com/searxng/searxng/pull/1412/files
- https://github.com/searxng/searxng/pull/1356
In my opinion, TypeDict is unsuitable because the objects are still dictionaries
and not instances of classes / the `dataclass` are classes but ...
The `msgspec.Struct` combine the advantages of typing, runtime behaviour and
also offer the option of (fast) serializing (incl. type check) the objects.
Currently not possible but conceivable with `msgspec`: Outsourcing the engines
into separate processes, what possibilities this opens up in the future is left
to the imagination!
Internally, we have already defined that it is desirable to decouple the
development of the engines from the development of the SearXNG core / The
serialization of the `Result` objects is a prerequisite for this.
HINT: The threads listed above were the template for this PR, even though the
implementation here is based on msgspec. They should also be an inspiration for
the following PRs of typification, as the models and implementations can provide
a good direction.
Why just one commit?
====================
I tried to create several (thematically separated) commits, but gave up at some
point ... there are too many things to tackle at once / The comprehensibility of
the commits would not be improved by a thematic separation. On the contrary, we
would have to make multiple changes at the same places and the goal of a change
would be vaguely recognizable in the fog of the commits.
Signed-off-by: Markus Heiser <markus.heiser@darmarit.de>
2024-12-15 09:59:50 +01:00
|
|
|
import lxml.etree
|
|
|
|
import lxml.html
|
2021-03-18 19:59:01 +01:00
|
|
|
from httpx import HTTPError
|
|
|
|
|
[refactor] typification of SearXNG (initial) / result items (part 1)
Typification of SearXNG
=======================
This patch introduces the typing of the results. The why and how is described
in the documentation, please generate the documentation ..
$ make docs.clean docs.live
and read the following articles in the "Developer documentation":
- result types --> http://0.0.0.0:8000/dev/result_types/index.html
The result types are available from the `searx.result_types` module. The
following have been implemented so far:
- base result type: `searx.result_type.Result`
--> http://0.0.0.0:8000/dev/result_types/base_result.html
- answer results
--> http://0.0.0.0:8000/dev/result_types/answer.html
including the type for translations (inspired by #3925). For all other
types (which still need to be set up in subsequent PRs), template documentation
has been created for the transition period.
Doc of the fields used in Templates
===================================
The template documentation is the basis for the typing and is the first complete
documentation of the results (needed for engine development). It is the
"working paper" (the plan) with which further typifications can be implemented
in subsequent PRs.
- https://github.com/searxng/searxng/issues/357
Answer Templates
================
With the new (sub) types for `Answer`, the templates for the answers have also
been revised, `Translation` are now displayed with collapsible entries (inspired
by #3925).
!en-de dog
Plugins & Answerer
==================
The implementation for `Plugin` and `Answer` has been revised, see
documentation:
- Plugin: http://0.0.0.0:8000/dev/plugins/index.html
- Answerer: http://0.0.0.0:8000/dev/answerers/index.html
With `AnswerStorage` and `AnswerStorage` to manage those items (in follow up
PRs, `ArticleStorage`, `InfoStorage` and .. will be implemented)
Autocomplete
============
The autocompletion had a bug where the results from `Answer` had not been shown
in the past. To test activate autocompletion and try search terms for which we
have answerers
- statistics: type `min 1 2 3` .. in the completion list you should find an
entry like `[de] min(1, 2, 3) = 1`
- random: type `random uuid` .. in the completion list, the first item is a
random UUID
Extended Types
==============
SearXNG extends e.g. the request and response types of flask and httpx, a module
has been set up for type extensions:
- Extended Types
--> http://0.0.0.0:8000/dev/extended_types.html
Unit-Tests
==========
The unit tests have been completely revised. In the previous implementation,
the runtime (the global variables such as `searx.settings`) was not initialized
before each test, so the runtime environment with which a test ran was always
determined by the tests that ran before it. This was also the reason why we
sometimes had to observe non-deterministic errors in the tests in the past:
- https://github.com/searxng/searxng/issues/2988 is one example for the Runtime
issues, with non-deterministic behavior ..
- https://github.com/searxng/searxng/pull/3650
- https://github.com/searxng/searxng/pull/3654
- https://github.com/searxng/searxng/pull/3642#issuecomment-2226884469
- https://github.com/searxng/searxng/pull/3746#issuecomment-2300965005
Why msgspec.Struct
==================
We have already discussed typing based on e.g. `TypeDict` or `dataclass` in the past:
- https://github.com/searxng/searxng/pull/1562/files
- https://gist.github.com/dalf/972eb05e7a9bee161487132a7de244d2
- https://github.com/searxng/searxng/pull/1412/files
- https://github.com/searxng/searxng/pull/1356
In my opinion, TypeDict is unsuitable because the objects are still dictionaries
and not instances of classes / the `dataclass` are classes but ...
The `msgspec.Struct` combine the advantages of typing, runtime behaviour and
also offer the option of (fast) serializing (incl. type check) the objects.
Currently not possible but conceivable with `msgspec`: Outsourcing the engines
into separate processes, what possibilities this opens up in the future is left
to the imagination!
Internally, we have already defined that it is desirable to decouple the
development of the engines from the development of the SearXNG core / The
serialization of the `Result` objects is a prerequisite for this.
HINT: The threads listed above were the template for this PR, even though the
implementation here is based on msgspec. They should also be an inspiration for
the following PRs of typification, as the models and implementations can provide
a good direction.
Why just one commit?
====================
I tried to create several (thematically separated) commits, but gave up at some
point ... there are too many things to tackle at once / The comprehensibility of
the commits would not be improved by a thematic separation. On the contrary, we
would have to make multiple changes at the same places and the goal of a change
would be vaguely recognizable in the fog of the commits.
Signed-off-by: Markus Heiser <markus.heiser@darmarit.de>
2024-12-15 09:59:50 +01:00
|
|
|
from searx.extended_types import SXNG_Response
|
2015-04-10 00:59:25 +02:00
|
|
|
from searx import settings
|
2022-12-04 22:57:22 +01:00
|
|
|
from searx.engines import (
|
|
|
|
engines,
|
|
|
|
google,
|
|
|
|
)
|
2024-01-05 18:15:42 +01:00
|
|
|
from searx.network import get as http_get, post as http_post
|
2021-02-22 18:13:50 +01:00
|
|
|
from searx.exceptions import SearxEngineResponseException
|
2018-01-18 20:51:27 -06:00
|
|
|
|
2015-04-10 00:59:25 +02:00
|
|
|
|
2024-01-05 18:15:42 +01:00
|
|
|
def update_kwargs(**kwargs):
|
2015-05-02 15:45:17 +02:00
|
|
|
if 'timeout' not in kwargs:
|
2015-08-02 19:38:27 +02:00
|
|
|
kwargs['timeout'] = settings['outgoing']['request_timeout']
|
2021-02-22 18:13:50 +01:00
|
|
|
kwargs['raise_for_httperror'] = True
|
2024-01-05 18:15:42 +01:00
|
|
|
|
|
|
|
|
[refactor] typification of SearXNG (initial) / result items (part 1)
Typification of SearXNG
=======================
This patch introduces the typing of the results. The why and how is described
in the documentation, please generate the documentation ..
$ make docs.clean docs.live
and read the following articles in the "Developer documentation":
- result types --> http://0.0.0.0:8000/dev/result_types/index.html
The result types are available from the `searx.result_types` module. The
following have been implemented so far:
- base result type: `searx.result_type.Result`
--> http://0.0.0.0:8000/dev/result_types/base_result.html
- answer results
--> http://0.0.0.0:8000/dev/result_types/answer.html
including the type for translations (inspired by #3925). For all other
types (which still need to be set up in subsequent PRs), template documentation
has been created for the transition period.
Doc of the fields used in Templates
===================================
The template documentation is the basis for the typing and is the first complete
documentation of the results (needed for engine development). It is the
"working paper" (the plan) with which further typifications can be implemented
in subsequent PRs.
- https://github.com/searxng/searxng/issues/357
Answer Templates
================
With the new (sub) types for `Answer`, the templates for the answers have also
been revised, `Translation` are now displayed with collapsible entries (inspired
by #3925).
!en-de dog
Plugins & Answerer
==================
The implementation for `Plugin` and `Answer` has been revised, see
documentation:
- Plugin: http://0.0.0.0:8000/dev/plugins/index.html
- Answerer: http://0.0.0.0:8000/dev/answerers/index.html
With `AnswerStorage` and `AnswerStorage` to manage those items (in follow up
PRs, `ArticleStorage`, `InfoStorage` and .. will be implemented)
Autocomplete
============
The autocompletion had a bug where the results from `Answer` had not been shown
in the past. To test activate autocompletion and try search terms for which we
have answerers
- statistics: type `min 1 2 3` .. in the completion list you should find an
entry like `[de] min(1, 2, 3) = 1`
- random: type `random uuid` .. in the completion list, the first item is a
random UUID
Extended Types
==============
SearXNG extends e.g. the request and response types of flask and httpx, a module
has been set up for type extensions:
- Extended Types
--> http://0.0.0.0:8000/dev/extended_types.html
Unit-Tests
==========
The unit tests have been completely revised. In the previous implementation,
the runtime (the global variables such as `searx.settings`) was not initialized
before each test, so the runtime environment with which a test ran was always
determined by the tests that ran before it. This was also the reason why we
sometimes had to observe non-deterministic errors in the tests in the past:
- https://github.com/searxng/searxng/issues/2988 is one example for the Runtime
issues, with non-deterministic behavior ..
- https://github.com/searxng/searxng/pull/3650
- https://github.com/searxng/searxng/pull/3654
- https://github.com/searxng/searxng/pull/3642#issuecomment-2226884469
- https://github.com/searxng/searxng/pull/3746#issuecomment-2300965005
Why msgspec.Struct
==================
We have already discussed typing based on e.g. `TypeDict` or `dataclass` in the past:
- https://github.com/searxng/searxng/pull/1562/files
- https://gist.github.com/dalf/972eb05e7a9bee161487132a7de244d2
- https://github.com/searxng/searxng/pull/1412/files
- https://github.com/searxng/searxng/pull/1356
In my opinion, TypeDict is unsuitable because the objects are still dictionaries
and not instances of classes / the `dataclass` are classes but ...
The `msgspec.Struct` combine the advantages of typing, runtime behaviour and
also offer the option of (fast) serializing (incl. type check) the objects.
Currently not possible but conceivable with `msgspec`: Outsourcing the engines
into separate processes, what possibilities this opens up in the future is left
to the imagination!
Internally, we have already defined that it is desirable to decouple the
development of the engines from the development of the SearXNG core / The
serialization of the `Result` objects is a prerequisite for this.
HINT: The threads listed above were the template for this PR, even though the
implementation here is based on msgspec. They should also be an inspiration for
the following PRs of typification, as the models and implementations can provide
a good direction.
Why just one commit?
====================
I tried to create several (thematically separated) commits, but gave up at some
point ... there are too many things to tackle at once / The comprehensibility of
the commits would not be improved by a thematic separation. On the contrary, we
would have to make multiple changes at the same places and the goal of a change
would be vaguely recognizable in the fog of the commits.
Signed-off-by: Markus Heiser <markus.heiser@darmarit.de>
2024-12-15 09:59:50 +01:00
|
|
|
def get(*args, **kwargs) -> SXNG_Response:
|
2024-01-05 18:15:42 +01:00
|
|
|
update_kwargs(**kwargs)
|
2015-04-10 00:59:25 +02:00
|
|
|
return http_get(*args, **kwargs)
|
2015-01-10 16:42:57 +01:00
|
|
|
|
|
|
|
|
[refactor] typification of SearXNG (initial) / result items (part 1)
Typification of SearXNG
=======================
This patch introduces the typing of the results. The why and how is described
in the documentation, please generate the documentation ..
$ make docs.clean docs.live
and read the following articles in the "Developer documentation":
- result types --> http://0.0.0.0:8000/dev/result_types/index.html
The result types are available from the `searx.result_types` module. The
following have been implemented so far:
- base result type: `searx.result_type.Result`
--> http://0.0.0.0:8000/dev/result_types/base_result.html
- answer results
--> http://0.0.0.0:8000/dev/result_types/answer.html
including the type for translations (inspired by #3925). For all other
types (which still need to be set up in subsequent PRs), template documentation
has been created for the transition period.
Doc of the fields used in Templates
===================================
The template documentation is the basis for the typing and is the first complete
documentation of the results (needed for engine development). It is the
"working paper" (the plan) with which further typifications can be implemented
in subsequent PRs.
- https://github.com/searxng/searxng/issues/357
Answer Templates
================
With the new (sub) types for `Answer`, the templates for the answers have also
been revised, `Translation` are now displayed with collapsible entries (inspired
by #3925).
!en-de dog
Plugins & Answerer
==================
The implementation for `Plugin` and `Answer` has been revised, see
documentation:
- Plugin: http://0.0.0.0:8000/dev/plugins/index.html
- Answerer: http://0.0.0.0:8000/dev/answerers/index.html
With `AnswerStorage` and `AnswerStorage` to manage those items (in follow up
PRs, `ArticleStorage`, `InfoStorage` and .. will be implemented)
Autocomplete
============
The autocompletion had a bug where the results from `Answer` had not been shown
in the past. To test activate autocompletion and try search terms for which we
have answerers
- statistics: type `min 1 2 3` .. in the completion list you should find an
entry like `[de] min(1, 2, 3) = 1`
- random: type `random uuid` .. in the completion list, the first item is a
random UUID
Extended Types
==============
SearXNG extends e.g. the request and response types of flask and httpx, a module
has been set up for type extensions:
- Extended Types
--> http://0.0.0.0:8000/dev/extended_types.html
Unit-Tests
==========
The unit tests have been completely revised. In the previous implementation,
the runtime (the global variables such as `searx.settings`) was not initialized
before each test, so the runtime environment with which a test ran was always
determined by the tests that ran before it. This was also the reason why we
sometimes had to observe non-deterministic errors in the tests in the past:
- https://github.com/searxng/searxng/issues/2988 is one example for the Runtime
issues, with non-deterministic behavior ..
- https://github.com/searxng/searxng/pull/3650
- https://github.com/searxng/searxng/pull/3654
- https://github.com/searxng/searxng/pull/3642#issuecomment-2226884469
- https://github.com/searxng/searxng/pull/3746#issuecomment-2300965005
Why msgspec.Struct
==================
We have already discussed typing based on e.g. `TypeDict` or `dataclass` in the past:
- https://github.com/searxng/searxng/pull/1562/files
- https://gist.github.com/dalf/972eb05e7a9bee161487132a7de244d2
- https://github.com/searxng/searxng/pull/1412/files
- https://github.com/searxng/searxng/pull/1356
In my opinion, TypeDict is unsuitable because the objects are still dictionaries
and not instances of classes / the `dataclass` are classes but ...
The `msgspec.Struct` combine the advantages of typing, runtime behaviour and
also offer the option of (fast) serializing (incl. type check) the objects.
Currently not possible but conceivable with `msgspec`: Outsourcing the engines
into separate processes, what possibilities this opens up in the future is left
to the imagination!
Internally, we have already defined that it is desirable to decouple the
development of the engines from the development of the SearXNG core / The
serialization of the `Result` objects is a prerequisite for this.
HINT: The threads listed above were the template for this PR, even though the
implementation here is based on msgspec. They should also be an inspiration for
the following PRs of typification, as the models and implementations can provide
a good direction.
Why just one commit?
====================
I tried to create several (thematically separated) commits, but gave up at some
point ... there are too many things to tackle at once / The comprehensibility of
the commits would not be improved by a thematic separation. On the contrary, we
would have to make multiple changes at the same places and the goal of a change
would be vaguely recognizable in the fog of the commits.
Signed-off-by: Markus Heiser <markus.heiser@darmarit.de>
2024-12-15 09:59:50 +01:00
|
|
|
def post(*args, **kwargs) -> SXNG_Response:
|
2024-01-05 18:15:42 +01:00
|
|
|
update_kwargs(**kwargs)
|
|
|
|
return http_post(*args, **kwargs)
|
|
|
|
|
|
|
|
|
2025-01-25 18:59:10 +08:00
|
|
|
def baidu(query, _lang):
|
|
|
|
# baidu search autocompleter
|
|
|
|
base_url = "https://www.baidu.com/sugrec?"
|
|
|
|
response = get(base_url + urlencode({'ie': 'utf-8', 'json': 1, 'prod': 'pc', 'wd': query}))
|
|
|
|
|
|
|
|
results = []
|
|
|
|
|
|
|
|
if response.ok:
|
|
|
|
data = response.json()
|
|
|
|
if 'g' in data:
|
|
|
|
for item in data['g']:
|
|
|
|
results.append(item['q'])
|
|
|
|
return results
|
|
|
|
|
|
|
|
|
2022-01-19 17:25:24 +01:00
|
|
|
def brave(query, _lang):
|
2022-01-02 23:05:49 +01:00
|
|
|
# brave search autocompleter
|
2022-01-19 17:25:24 +01:00
|
|
|
url = 'https://search.brave.com/api/suggest?'
|
|
|
|
url += urlencode({'q': query})
|
|
|
|
country = 'all'
|
|
|
|
# if lang in _brave:
|
|
|
|
# country = lang
|
|
|
|
kwargs = {'cookies': {'country': country}}
|
|
|
|
resp = get(url, **kwargs)
|
2022-01-02 23:05:49 +01:00
|
|
|
|
|
|
|
results = []
|
|
|
|
|
|
|
|
if resp.ok:
|
2022-01-23 17:22:13 +01:00
|
|
|
data = resp.json()
|
2022-01-02 23:05:49 +01:00
|
|
|
for item in data[1]:
|
|
|
|
results.append(item)
|
|
|
|
return results
|
|
|
|
|
|
|
|
|
2022-01-19 17:25:24 +01:00
|
|
|
def dbpedia(query, _lang):
|
2015-05-02 11:43:12 +02:00
|
|
|
# dbpedia autocompleter, no HTTPS
|
2020-12-04 16:47:43 +01:00
|
|
|
autocomplete_url = 'https://lookup.dbpedia.org/api/search.asmx/KeywordSearch?'
|
2014-03-29 16:30:49 +01:00
|
|
|
|
2016-01-18 12:47:31 +01:00
|
|
|
response = get(autocomplete_url + urlencode(dict(QueryString=query)))
|
2014-03-29 16:30:49 +01:00
|
|
|
|
|
|
|
results = []
|
|
|
|
|
|
|
|
if response.ok:
|
2022-12-04 22:57:22 +01:00
|
|
|
dom = lxml.etree.fromstring(response.content)
|
2020-12-04 16:47:43 +01:00
|
|
|
results = dom.xpath('//Result/Label//text()')
|
2014-03-29 16:30:49 +01:00
|
|
|
|
|
|
|
return results
|
|
|
|
|
|
|
|
|
2022-11-05 15:10:52 +01:00
|
|
|
def duckduckgo(query, sxng_locale):
|
|
|
|
"""Autocomplete from DuckDuckGo. Supports DuckDuckGo's languages"""
|
|
|
|
|
|
|
|
traits = engines['duckduckgo'].traits
|
|
|
|
args = {
|
|
|
|
'q': query,
|
|
|
|
'kl': traits.get_region(sxng_locale, traits.all_locale),
|
|
|
|
}
|
|
|
|
|
|
|
|
url = 'https://duckduckgo.com/ac/?type=list&' + urlencode(args)
|
|
|
|
resp = get(url)
|
|
|
|
|
|
|
|
ret_val = []
|
|
|
|
if resp.ok:
|
|
|
|
j = resp.json()
|
|
|
|
if len(j) > 1:
|
|
|
|
ret_val = j[1]
|
|
|
|
return ret_val
|
2014-09-07 23:56:06 +02:00
|
|
|
|
|
|
|
|
2022-12-04 22:57:22 +01:00
|
|
|
def google_complete(query, sxng_locale):
|
|
|
|
"""Autocomplete from Google. Supports Google's languages and subdomains
|
|
|
|
(:py:obj:`searx.engines.google.get_google_info`) by using the async REST
|
|
|
|
API::
|
2014-03-29 16:30:49 +01:00
|
|
|
|
2022-12-04 22:57:22 +01:00
|
|
|
https://{subdomain}/complete/search?{args}
|
2014-03-29 16:30:49 +01:00
|
|
|
|
2022-12-04 22:57:22 +01:00
|
|
|
"""
|
2014-03-29 16:30:49 +01:00
|
|
|
|
2022-12-04 22:57:22 +01:00
|
|
|
google_info = google.get_google_info({'searxng_locale': sxng_locale}, engines['google'].traits)
|
2014-03-29 16:30:49 +01:00
|
|
|
|
2022-12-04 22:57:22 +01:00
|
|
|
url = 'https://{subdomain}/complete/search?{args}'
|
|
|
|
args = urlencode(
|
|
|
|
{
|
|
|
|
'q': query,
|
|
|
|
'client': 'gws-wiz',
|
|
|
|
'hl': google_info['params']['hl'],
|
|
|
|
}
|
|
|
|
)
|
|
|
|
results = []
|
|
|
|
resp = get(url.format(subdomain=google_info['subdomain'], args=args))
|
[refactor] typification of SearXNG (initial) / result items (part 1)
Typification of SearXNG
=======================
This patch introduces the typing of the results. The why and how is described
in the documentation, please generate the documentation ..
$ make docs.clean docs.live
and read the following articles in the "Developer documentation":
- result types --> http://0.0.0.0:8000/dev/result_types/index.html
The result types are available from the `searx.result_types` module. The
following have been implemented so far:
- base result type: `searx.result_type.Result`
--> http://0.0.0.0:8000/dev/result_types/base_result.html
- answer results
--> http://0.0.0.0:8000/dev/result_types/answer.html
including the type for translations (inspired by #3925). For all other
types (which still need to be set up in subsequent PRs), template documentation
has been created for the transition period.
Doc of the fields used in Templates
===================================
The template documentation is the basis for the typing and is the first complete
documentation of the results (needed for engine development). It is the
"working paper" (the plan) with which further typifications can be implemented
in subsequent PRs.
- https://github.com/searxng/searxng/issues/357
Answer Templates
================
With the new (sub) types for `Answer`, the templates for the answers have also
been revised, `Translation` are now displayed with collapsible entries (inspired
by #3925).
!en-de dog
Plugins & Answerer
==================
The implementation for `Plugin` and `Answer` has been revised, see
documentation:
- Plugin: http://0.0.0.0:8000/dev/plugins/index.html
- Answerer: http://0.0.0.0:8000/dev/answerers/index.html
With `AnswerStorage` and `AnswerStorage` to manage those items (in follow up
PRs, `ArticleStorage`, `InfoStorage` and .. will be implemented)
Autocomplete
============
The autocompletion had a bug where the results from `Answer` had not been shown
in the past. To test activate autocompletion and try search terms for which we
have answerers
- statistics: type `min 1 2 3` .. in the completion list you should find an
entry like `[de] min(1, 2, 3) = 1`
- random: type `random uuid` .. in the completion list, the first item is a
random UUID
Extended Types
==============
SearXNG extends e.g. the request and response types of flask and httpx, a module
has been set up for type extensions:
- Extended Types
--> http://0.0.0.0:8000/dev/extended_types.html
Unit-Tests
==========
The unit tests have been completely revised. In the previous implementation,
the runtime (the global variables such as `searx.settings`) was not initialized
before each test, so the runtime environment with which a test ran was always
determined by the tests that ran before it. This was also the reason why we
sometimes had to observe non-deterministic errors in the tests in the past:
- https://github.com/searxng/searxng/issues/2988 is one example for the Runtime
issues, with non-deterministic behavior ..
- https://github.com/searxng/searxng/pull/3650
- https://github.com/searxng/searxng/pull/3654
- https://github.com/searxng/searxng/pull/3642#issuecomment-2226884469
- https://github.com/searxng/searxng/pull/3746#issuecomment-2300965005
Why msgspec.Struct
==================
We have already discussed typing based on e.g. `TypeDict` or `dataclass` in the past:
- https://github.com/searxng/searxng/pull/1562/files
- https://gist.github.com/dalf/972eb05e7a9bee161487132a7de244d2
- https://github.com/searxng/searxng/pull/1412/files
- https://github.com/searxng/searxng/pull/1356
In my opinion, TypeDict is unsuitable because the objects are still dictionaries
and not instances of classes / the `dataclass` are classes but ...
The `msgspec.Struct` combine the advantages of typing, runtime behaviour and
also offer the option of (fast) serializing (incl. type check) the objects.
Currently not possible but conceivable with `msgspec`: Outsourcing the engines
into separate processes, what possibilities this opens up in the future is left
to the imagination!
Internally, we have already defined that it is desirable to decouple the
development of the engines from the development of the SearXNG core / The
serialization of the `Result` objects is a prerequisite for this.
HINT: The threads listed above were the template for this PR, even though the
implementation here is based on msgspec. They should also be an inspiration for
the following PRs of typification, as the models and implementations can provide
a good direction.
Why just one commit?
====================
I tried to create several (thematically separated) commits, but gave up at some
point ... there are too many things to tackle at once / The comprehensibility of
the commits would not be improved by a thematic separation. On the contrary, we
would have to make multiple changes at the same places and the goal of a change
would be vaguely recognizable in the fog of the commits.
Signed-off-by: Markus Heiser <markus.heiser@darmarit.de>
2024-12-15 09:59:50 +01:00
|
|
|
if resp and resp.ok:
|
2022-12-04 22:57:22 +01:00
|
|
|
json_txt = resp.text[resp.text.find('[') : resp.text.find(']', -3) + 1]
|
|
|
|
data = json.loads(json_txt)
|
|
|
|
for item in data[0]:
|
|
|
|
results.append(lxml.html.fromstring(item[0]).text_content())
|
2014-03-29 16:30:49 +01:00
|
|
|
return results
|
|
|
|
|
|
|
|
|
2023-08-23 15:24:42 +02:00
|
|
|
def mwmbl(query, _lang):
|
2023-08-23 23:13:46 +02:00
|
|
|
"""Autocomplete from Mwmbl_."""
|
|
|
|
|
2023-08-23 15:24:42 +02:00
|
|
|
# mwmbl autocompleter
|
|
|
|
url = 'https://api.mwmbl.org/search/complete?{query}'
|
|
|
|
|
|
|
|
results = get(url.format(query=urlencode({'q': query}))).json()[1]
|
|
|
|
|
|
|
|
# results starting with `go:` are direct urls and not useful for auto completion
|
|
|
|
return [result for result in results if not result.startswith("go: ") and not result.startswith("search: ")]
|
|
|
|
|
|
|
|
|
2022-04-14 03:02:05 +02:00
|
|
|
def seznam(query, _lang):
|
|
|
|
# seznam search autocompleter
|
|
|
|
url = 'https://suggest.seznam.cz/fulltext/cs?{query}'
|
|
|
|
|
2022-05-07 18:23:10 +02:00
|
|
|
resp = get(
|
|
|
|
url.format(
|
|
|
|
query=urlencode(
|
|
|
|
{'phrase': query, 'cursorPosition': len(query), 'format': 'json-2', 'highlight': '1', 'count': '6'}
|
|
|
|
)
|
|
|
|
)
|
|
|
|
)
|
2022-04-14 03:02:05 +02:00
|
|
|
|
|
|
|
if not resp.ok:
|
|
|
|
return []
|
|
|
|
|
|
|
|
data = resp.json()
|
2022-05-07 18:23:10 +02:00
|
|
|
return [
|
|
|
|
''.join([part.get('text', '') for part in item.get('text', [])])
|
|
|
|
for item in data.get('result', [])
|
|
|
|
if item.get('itemType', None) == 'ItemType.TEXT'
|
|
|
|
]
|
|
|
|
|
2022-04-14 03:02:05 +02:00
|
|
|
|
2024-01-05 18:15:42 +01:00
|
|
|
def stract(query, _lang):
|
|
|
|
# stract autocompleter (beta)
|
|
|
|
url = f"https://stract.com/beta/api/autosuggest?q={quote_plus(query)}"
|
|
|
|
|
|
|
|
resp = post(url)
|
|
|
|
|
|
|
|
if not resp.ok:
|
|
|
|
return []
|
|
|
|
|
2024-07-01 16:45:20 +00:00
|
|
|
return [html.unescape(suggestion['raw']) for suggestion in resp.json()]
|
2024-01-05 18:15:42 +01:00
|
|
|
|
|
|
|
|
2022-10-30 11:23:20 +01:00
|
|
|
def startpage(query, sxng_locale):
|
|
|
|
"""Autocomplete from Startpage. Supports Startpage's languages"""
|
|
|
|
lui = engines['startpage'].traits.get_language(sxng_locale, 'english')
|
2021-11-13 13:26:47 +01:00
|
|
|
url = 'https://startpage.com/suggestions?{query}'
|
|
|
|
resp = get(url.format(query=urlencode({'q': query, 'segment': 'startpage.udog', 'lui': lui})))
|
|
|
|
data = resp.json()
|
|
|
|
return [e['text'] for e in data.get('suggestions', []) if 'text' in e]
|
2015-06-01 20:45:18 +02:00
|
|
|
|
|
|
|
|
2022-01-19 17:25:24 +01:00
|
|
|
def swisscows(query, _lang):
|
2020-02-14 19:19:24 +01:00
|
|
|
# swisscows autocompleter
|
|
|
|
url = 'https://swisscows.ch/api/suggest?{query}&itemsCount=5'
|
|
|
|
|
2022-12-04 22:57:22 +01:00
|
|
|
resp = json.loads(get(url.format(query=urlencode({'query': query}))).text)
|
2020-02-14 19:19:24 +01:00
|
|
|
return resp
|
|
|
|
|
|
|
|
|
2022-10-03 22:42:58 +02:00
|
|
|
def qwant(query, sxng_locale):
|
|
|
|
"""Autocomplete from Qwant. Supports Qwant's regions."""
|
2016-03-02 19:54:06 +08:00
|
|
|
results = []
|
|
|
|
|
2022-10-03 22:42:58 +02:00
|
|
|
locale = engines['qwant'].traits.get_region(sxng_locale, 'en_US')
|
|
|
|
url = 'https://api.qwant.com/v3/suggest?{query}'
|
|
|
|
resp = get(url.format(query=urlencode({'q': query, 'locale': locale, 'version': '2'})))
|
|
|
|
|
2016-03-02 19:54:06 +08:00
|
|
|
if resp.ok:
|
2022-10-03 22:42:58 +02:00
|
|
|
data = resp.json()
|
2016-03-02 19:54:06 +08:00
|
|
|
if data['status'] == 'success':
|
|
|
|
for item in data['data']['items']:
|
|
|
|
results.append(item['value'])
|
|
|
|
|
|
|
|
return results
|
|
|
|
|
|
|
|
|
2022-10-28 19:12:59 +02:00
|
|
|
def wikipedia(query, sxng_locale):
|
|
|
|
"""Autocomplete from Wikipedia. Supports Wikipedia's languages (aka netloc)."""
|
|
|
|
results = []
|
|
|
|
eng_traits = engines['wikipedia'].traits
|
|
|
|
wiki_lang = eng_traits.get_language(sxng_locale, 'en')
|
[refactor] typification of SearXNG (initial) / result items (part 1)
Typification of SearXNG
=======================
This patch introduces the typing of the results. The why and how is described
in the documentation, please generate the documentation ..
$ make docs.clean docs.live
and read the following articles in the "Developer documentation":
- result types --> http://0.0.0.0:8000/dev/result_types/index.html
The result types are available from the `searx.result_types` module. The
following have been implemented so far:
- base result type: `searx.result_type.Result`
--> http://0.0.0.0:8000/dev/result_types/base_result.html
- answer results
--> http://0.0.0.0:8000/dev/result_types/answer.html
including the type for translations (inspired by #3925). For all other
types (which still need to be set up in subsequent PRs), template documentation
has been created for the transition period.
Doc of the fields used in Templates
===================================
The template documentation is the basis for the typing and is the first complete
documentation of the results (needed for engine development). It is the
"working paper" (the plan) with which further typifications can be implemented
in subsequent PRs.
- https://github.com/searxng/searxng/issues/357
Answer Templates
================
With the new (sub) types for `Answer`, the templates for the answers have also
been revised, `Translation` are now displayed with collapsible entries (inspired
by #3925).
!en-de dog
Plugins & Answerer
==================
The implementation for `Plugin` and `Answer` has been revised, see
documentation:
- Plugin: http://0.0.0.0:8000/dev/plugins/index.html
- Answerer: http://0.0.0.0:8000/dev/answerers/index.html
With `AnswerStorage` and `AnswerStorage` to manage those items (in follow up
PRs, `ArticleStorage`, `InfoStorage` and .. will be implemented)
Autocomplete
============
The autocompletion had a bug where the results from `Answer` had not been shown
in the past. To test activate autocompletion and try search terms for which we
have answerers
- statistics: type `min 1 2 3` .. in the completion list you should find an
entry like `[de] min(1, 2, 3) = 1`
- random: type `random uuid` .. in the completion list, the first item is a
random UUID
Extended Types
==============
SearXNG extends e.g. the request and response types of flask and httpx, a module
has been set up for type extensions:
- Extended Types
--> http://0.0.0.0:8000/dev/extended_types.html
Unit-Tests
==========
The unit tests have been completely revised. In the previous implementation,
the runtime (the global variables such as `searx.settings`) was not initialized
before each test, so the runtime environment with which a test ran was always
determined by the tests that ran before it. This was also the reason why we
sometimes had to observe non-deterministic errors in the tests in the past:
- https://github.com/searxng/searxng/issues/2988 is one example for the Runtime
issues, with non-deterministic behavior ..
- https://github.com/searxng/searxng/pull/3650
- https://github.com/searxng/searxng/pull/3654
- https://github.com/searxng/searxng/pull/3642#issuecomment-2226884469
- https://github.com/searxng/searxng/pull/3746#issuecomment-2300965005
Why msgspec.Struct
==================
We have already discussed typing based on e.g. `TypeDict` or `dataclass` in the past:
- https://github.com/searxng/searxng/pull/1562/files
- https://gist.github.com/dalf/972eb05e7a9bee161487132a7de244d2
- https://github.com/searxng/searxng/pull/1412/files
- https://github.com/searxng/searxng/pull/1356
In my opinion, TypeDict is unsuitable because the objects are still dictionaries
and not instances of classes / the `dataclass` are classes but ...
The `msgspec.Struct` combine the advantages of typing, runtime behaviour and
also offer the option of (fast) serializing (incl. type check) the objects.
Currently not possible but conceivable with `msgspec`: Outsourcing the engines
into separate processes, what possibilities this opens up in the future is left
to the imagination!
Internally, we have already defined that it is desirable to decouple the
development of the engines from the development of the SearXNG core / The
serialization of the `Result` objects is a prerequisite for this.
HINT: The threads listed above were the template for this PR, even though the
implementation here is based on msgspec. They should also be an inspiration for
the following PRs of typification, as the models and implementations can provide
a good direction.
Why just one commit?
====================
I tried to create several (thematically separated) commits, but gave up at some
point ... there are too many things to tackle at once / The comprehensibility of
the commits would not be improved by a thematic separation. On the contrary, we
would have to make multiple changes at the same places and the goal of a change
would be vaguely recognizable in the fog of the commits.
Signed-off-by: Markus Heiser <markus.heiser@darmarit.de>
2024-12-15 09:59:50 +01:00
|
|
|
wiki_netloc = eng_traits.custom['wiki_netloc'].get(wiki_lang, 'en.wikipedia.org') # type: ignore
|
2022-10-28 19:12:59 +02:00
|
|
|
|
|
|
|
url = 'https://{wiki_netloc}/w/api.php?{args}'
|
|
|
|
args = urlencode(
|
|
|
|
{
|
|
|
|
'action': 'opensearch',
|
|
|
|
'format': 'json',
|
|
|
|
'formatversion': '2',
|
|
|
|
'search': query,
|
|
|
|
'namespace': '0',
|
|
|
|
'limit': '10',
|
|
|
|
}
|
|
|
|
)
|
|
|
|
resp = get(url.format(args=args, wiki_netloc=wiki_netloc))
|
|
|
|
if resp.ok:
|
|
|
|
data = resp.json()
|
|
|
|
if len(data) > 1:
|
|
|
|
results = data[1]
|
2014-03-29 16:30:49 +01:00
|
|
|
|
2022-10-28 19:12:59 +02:00
|
|
|
return results
|
2014-03-29 16:30:49 +01:00
|
|
|
|
|
|
|
|
2022-09-09 23:42:44 +03:00
|
|
|
def yandex(query, _lang):
|
|
|
|
# yandex autocompleter
|
|
|
|
url = "https://suggest.yandex.com/suggest-ff.cgi?{0}"
|
|
|
|
|
2022-12-04 22:57:22 +01:00
|
|
|
resp = json.loads(get(url.format(urlencode(dict(part=query)))).text)
|
2022-09-09 23:42:44 +03:00
|
|
|
if len(resp) > 1:
|
|
|
|
return resp[1]
|
|
|
|
return []
|
|
|
|
|
|
|
|
|
2021-12-27 09:26:22 +01:00
|
|
|
backends = {
|
2025-01-25 18:59:10 +08:00
|
|
|
'baidu': baidu,
|
2025-01-25 12:02:10 +01:00
|
|
|
'brave': brave,
|
2021-12-27 09:26:22 +01:00
|
|
|
'dbpedia': dbpedia,
|
|
|
|
'duckduckgo': duckduckgo,
|
2022-12-04 22:57:22 +01:00
|
|
|
'google': google_complete,
|
2023-08-23 15:24:42 +02:00
|
|
|
'mwmbl': mwmbl,
|
2025-01-25 12:02:10 +01:00
|
|
|
'qwant': qwant,
|
2022-04-14 03:02:05 +02:00
|
|
|
'seznam': seznam,
|
2021-12-27 09:26:22 +01:00
|
|
|
'startpage': startpage,
|
2024-01-05 18:15:42 +01:00
|
|
|
'stract': stract,
|
2021-12-27 09:26:22 +01:00
|
|
|
'swisscows': swisscows,
|
|
|
|
'wikipedia': wikipedia,
|
2022-09-09 23:42:44 +03:00
|
|
|
'yandex': yandex,
|
2021-12-27 09:26:22 +01:00
|
|
|
}
|
2021-02-22 18:13:50 +01:00
|
|
|
|
|
|
|
|
2022-09-29 20:54:46 +02:00
|
|
|
def search_autocomplete(backend_name, query, sxng_locale):
|
2021-02-22 18:13:50 +01:00
|
|
|
backend = backends.get(backend_name)
|
|
|
|
if backend is None:
|
|
|
|
return []
|
|
|
|
try:
|
2022-09-29 20:54:46 +02:00
|
|
|
return backend(query, sxng_locale)
|
2021-03-18 19:59:01 +01:00
|
|
|
except (HTTPError, SearxEngineResponseException):
|
2021-02-22 18:13:50 +01:00
|
|
|
return []
|