From e1d33e7b655a4747dc6eb4a0c00864a3266fcd16 Mon Sep 17 00:00:00 2001 From: Andreas Maier Date: Wed, 31 Jul 2024 08:09:05 +0200 Subject: [PATCH] Fixed HTTP 400,14 on 'absolute-ifl-capping'' Signed-off-by: Andreas Maier --- docs/changes.rst | 5 +++++ examples/metrics.yaml | 2 +- 2 files changed, 6 insertions(+), 1 deletion(-) diff --git a/docs/changes.rst b/docs/changes.rst index 930a7e8a..700a4953 100644 --- a/docs/changes.rst +++ b/docs/changes.rst @@ -30,6 +30,11 @@ Released: not yet **Bug fixes:** +* Fixed a bug in the metric definition file that lead to + HTTP error 400,14 "'absolute-ifl-capping'' is not a valid value for the + corresponding query parm". Please download the fixed metric definition file + from the repo. (issue #564) + * Addressed safety issues up to 2024-07-21. * In the Github Actions test workflow for Python 3.6 and 3.7, changed diff --git a/examples/metrics.yaml b/examples/metrics.yaml index 6c016d2f..3d2cc2fa 100644 --- a/examples/metrics.yaml +++ b/examples/metrics.yaml @@ -1624,7 +1624,7 @@ fetch_properties: if: "hmc_version >= (2,15)" # Actually SE 2.15.0 - property_name: number-reserved-ifl-processors if: "hmc_version >= (2,15)" # Actually SE 2.15.0 - - property_name: absolute-ifl-capping' + - property_name: absolute-ifl-capping if: "hmc_version < (2,16)" - property_name: initial-ifl-processing-weight if: "hmc_version < (2,16)"