No warning for incorrect config dictionary

[jwaiton]

As noticed by jgrocott, if you try to run MULE with a nonexistent config file, the error is obtuse:

Traceback (most recent call last):
  File "/home/e78368jw/Documents/MULE/bin/mule", line 49, in <module>
    pack(args.config)
  File "/home/e78368jw/Documents/MULE/packs/proc/proc.py", line 21, in proc
    match conf_dict['process']:
          ~~~~~~~~~^^^^^^^^^^^
KeyError: 'process'

There should be a catch in the binary if the config file isn't found.

UPDATE: 03/11/2025

This error is also caused by the 'process' key being input incorrectly, although I expect this issue to go beyond that specific key in the config being incorrect.

I think the way forward is to write tests inputting incorrect config parameters and ensuring the output is as expected (legible error, warning of the specific incorrect config parameter).

Ian has been graced with this task. 😸

[Ian0sborne]

In MULE/bin/mule.py in line 42 why is module_name defined using `{args.pack}' twice?

args = parser.parse_args()

# import pack and run
try:
    module_name = f'packs.{args.pack}.{args.pack}'
    pack = getattr(import_module(module_name), args.pack)
except ModuleNotFoundError:
    print(f"Failed to find pack {args.pack}")
    traceback.print_exc()
    exit(1)
else:
    pack(args.config)

[jwaiton]

In MULE/bin/mule.py in line 42 why is module_name defined using `{args.pack}' twice?

Because each pack's main 'executable' script is named after the folder. For example: the proc() function in proc.py is within the proc/ folder. So for the module name, its packs.proc.proc being folder.folder.script.