[checkmk-commits] [tribe29/checkmk] 454860: Fix all RemovedInMarshmallow4Warning warnings

Branch: refs/heads/master Home: https://github.com/tribe29/checkmk Commit: 454860a25039514f52171f85daa0787eb960d09d https://github.com/tribe29/checkmk/commit/454860a25039514f52171f85daa0787eb… Author: Max Linke <max.linke(a)tribe29.com> Date: 2022-02-10 (Thu, 10 Feb 2022) Changed paths: M cmk/fields/__init__.py M cmk/gui/plugins/openapi/endpoints/bi.py M cmk/gui/plugins/openapi/endpoints/rule/fields.py M cmk/gui/plugins/openapi/endpoints/ruleset/fields.py M cmk/utils/bi/bi_actions.py M cmk/utils/bi/bi_aggregation.py M cmk/utils/bi/bi_aggregation_functions.py M cmk/utils/bi/bi_lib.py M cmk/utils/bi/bi_node_vis.py M cmk/utils/bi/bi_packs.py M cmk/utils/bi/bi_rule.py M cmk/utils/bi/bi_rule_interface.py M cmk/utils/bi/bi_search.py Log Message: ----------- Fix all RemovedInMarshmallow4Warning warnings - replace marshmallow.fields with cmk.utils.fields when metadata warnings is thrown - update explicit args to new keywords Check that all warnings are removed by adding the pytest flag `-W error::DeprecationWarning:marshmallow.fields`. Unfortunately we cannot configure filterwarnings with the same effect in the pytest config, see [1] for some hints why this might be. My assumption is that the -W flag is passed directly to the python interpreter before pytest does it's own warning setup. [1] https://nedbatchelder.com/blog/201810/why_warnings_is_mysterious.html Change-Id: Ib66d091e738ff3ee8a938ee72aea0073df62c1e1