From cf599ecf1973287576f880b3b7af20569cb99f40 Mon Sep 17 00:00:00 2001 From: Douglas Raillard Date: Tue, 30 May 2023 12:16:27 +0100 Subject: [PATCH] tools/bisector: Fix ruamel usage of DEFAULT_MAPPING_TAG FIX Recent versions of ruamel.yaml changed DEFAULT_MAPPING_TAG from a string to a new non-hashable object. Ensure we use the tag name to avoid any exception. --- tools/bisector/bisector/bisector.py | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/tools/bisector/bisector/bisector.py b/tools/bisector/bisector/bisector.py index 82fc02090..14b84f5a0 100755 --- a/tools/bisector/bisector/bisector.py +++ b/tools/bisector/bisector/bisector.py @@ -3856,7 +3856,7 @@ class Report(Serializable): return collections.OrderedDict(loader.construct_pairs(node)) yaml.representer.add_representer(collections.OrderedDict, map_representer) - yaml.constructor.add_constructor(yaml.resolver.DEFAULT_MAPPING_TAG, map_constructor) + yaml.constructor.add_constructor(str(yaml.resolver.DEFAULT_MAPPING_TAG), map_constructor) # Since strings are immutable, we can memoized the output to deduplicate # strings. -- GitLab