This project is mirrored from Pull mirroring failed .
Repository mirroring has been paused due to too many failed attempts. It can be resumed by a project maintainer.
  1. 28 Oct, 2021 2 commits
  2. 25 Oct, 2021 1 commit
  3. 22 Oct, 2021 6 commits
  4. 21 Oct, 2021 1 commit
  5. 12 Oct, 2021 1 commit
  6. 10 Oct, 2021 19 commits
  7. 08 Oct, 2021 2 commits
  8. 06 Oct, 2021 1 commit
    • Simon Schuster's avatar
      [fix] use engine-type when looking up supported_languages from JSON files · 23d6c9c7
      Simon Schuster authored
      searx/data/engines_languages.json stores language information for
      several searchengines in a json endoded dict that maps engine-"types" to
      their supported languages; for instance there is an entry "google",
      mapping to the supported languages of the google engine.
      However, the lookup code did not use the engine 'type' (as in: the
      filename searx/engines/<enginetype>.py), but instead the manually
      configured engine name from settings.yml when querying. This is
      problematic as soon as users start to specify additional engine
      instances with custom names in the config file, as for instance
      suggested as a workaround for multilingual search in the manual[0]:
      > engines:
      >   - name : google english
      >     engine : google
      >     language : english
      Here, the engine name "google english" will be used for the lookup in
      the json file, which does not exist. The empty supported_languages then
      lead to a type error later in the processing callchain.
      This patch changes the behaviour to use the engine's entry-"type"
      ("google" in the above example) for the lookup. This should fix bug #2928.
  9. 03 Oct, 2021 2 commits
  10. 02 Oct, 2021 5 commits