Inconsistent hangs when changing the logging level on the "Advanced Default" example

[trevorhardy]

Describe the bug

When running the HELICS Advanced Default example, changing the reported logging level in the code for each federate from DEBUG to INFO causes the federation to hang. Similar behavior was seen when changing to WARNING or ERROR.

To Reproduce

Steps to reproduce the behavior:

Run the advanced default example here with helics run --path=./advanced_default_runner.json. The committed version should have the logging level near the top of the file set to DEFAULT. Assuming this runs to completion, change logger.setLevel(logging.DEBUG) to logger.setLevel(logging.INFO) and rerun. The former should complete and the later should fail to complete.

Environment (please complete the following information):

• Operating System: 14.7.2
• Installation: Build HELICS 3.6.0 from source
• helics and pyhelics version:

helics --version
helics, version 3.6.0

Python HELICS version 3.6.0

HELICS Library version 3.6.0 (2024-12-09)

Share the output of the following:

$ python -c "import helics as h; import json; print(json.dumps(h.helicsGetSystemInfo(), indent=4, sort_keys=True))"
{
    "buildflags": " -O3 -DNDEBUG  $<$<COMPILE_LANGUAGE:CXX>:-std=c++20>",
    "compiler": "Unix Makefiles  Darwin-23.6.0:AppleClang-15.0.0.15000309",
    "cores": [
        "zmq",
        "zmqss",
        "tcp",
        "tcpss",
        "udp",
        "ipc",
        "interprocess",
        "inproc"
    ],
    "cpu": "Apple M1 Max",
    "cpucount": 10,
    "cputype": "arm64",
    "memory": "32768 MB",
    "os": "Darwin  23.6.0  Darwin Kernel Version 23.6.0: Fri Nov 15 15:13:15 PST 2024; root:xnu-10063.141.1.702.7~1/RELEASE_ARM64_T6000",
    "version": {
        "build": "",
        "major": 3,
        "minor": 6,
        "patch": 0,
        "string": "3.6.0 (2024-12-09)"
    },
    "zmqversion": "ZMQ v4.3.5"
}