Issue #5490 was caused by a regression of GH action in v6.0.0, updating to v6.0.1 [2] fixed our workflow and debug messages are no longer needed. [1] https://github.com/searxng/searxng/issues/5490#issuecomment-3616230451 [2] https://github.com/searxng/searxng/pull/5530 Signed-off-by: Markus Heiser <markus.heiser@darmarit.de>
The error only occurs in the CI action, which is why we need to commit the coded debug. As soon as the bug is identified and fixed, this commit can be reverted / the ``set -x`` can be removed from the code. Signed-off-by: Markus Heiser <markus.heiser@darmarit.de>
Since #5280 has been merged, msgspec, like yaml, is a fixed part of the SearXNG *settings framework* and therefore, like yaml, must be installed in the virtual environment before installing SearXNG (``searx``). The actual reason is that in SearXNG we store settings in the configuration that are required for the installation of the ``searx`` package. This means that these settings (from settings.yml) are read in during the installation, and all the necessary tools for this (pyyaml, msgspec, setuptools, etc.) must be installed beforehand (chicken or the egg dilemma). Related: - https://github.com/searxng/searxng/pull/5353 - https://github.com/searxng/searxng/pull/5346 - https://github.com/searxng/searxng/pull/5280 - https://github.com/searxng/searxng/pull/5254 Closes: https://github.com/searxng/searxng/issues/5357 Signed-off-by: Markus Heiser <markus.heiser@darmarit.de>
We only need updated podman on `build`. `test` and `release` can use image provided container engine binaries.
Since #5280 has been merged, msgspec, like yaml, is a fixed part of the SearXNG *settings framework* and therefore, like yaml, must be installed in the virtual environment before installing SearXNG (``searx``). The actual reason is that in SearXNG we store settings in the configuration that are required for the installation of the ``searx`` package. This means that these settings (from settings.yml) are read in during the installation, and all the necessary tools for this (pyyaml, msgspec, setuptools, etc.) must be installed beforehand (chicken or the egg dilemma). Related: - https://github.com/searxng/searxng/pull/5280 - https://github.com/searxng/searxng/pull/5254 Closes: https://github.com/searxng/searxng/issues/5343 Signed-off-by: Markus Heiser <markus.heiser@darmarit.de>
Last major update of Pylint brings some breaking changes [1], fixed in this patch. [1] https://pylint.readthedocs.io/en/latest/whatsnew/4/4.0/index.html#breaking-changes
Mise en place config [1] does no longer support ``.tool-versions`` compatibility syntax, migrate to TOML ``mise.toml``. In ``utils/lib_sxng_node.sh`` the node version was not updated, update to 24.3.0 (compare ``mise.toml``). [1] https://mise.jdx.dev/configuration.html Signed-off-by: Markus Heiser <markus.heiser@darmarit.de>
Docker buildx outputs the following error: variable expansion is not supported for --from, define a new stage with FROM using ARG from global scope as a workaround. Also force BuildKit extension to be installed, legacy build is no longer supported. Closes https://github.com/searxng/searxng/issues/5219
* [enh] container: reproducible layers We are not aiming for reproducibility compliance, but we look to make most builder layers reproducible without caching at least for a short period of time (until the builder's base image changes or the child dependencies of a requirements.txt package are updated). This feature is only available on Podman. This targets https://github.com/searxng/searxng/pull/5086 main goal. * [fix] misc: apply suggestions Suggested: https://github.com/searxng/searxng/pull/5222#discussion_r2364630496 Suggested: https://github.com/searxng/searxng/pull/5222#discussion_r2364630511 * [enh] container: prevent useless layer