layers order - config plugin - crash

[rhubert]

Describe the bug

Depending on the order of the layers I observed a crash.

Steps to reproduce

Unpack the attached reproducer + bob layers update + bob ls or any other command parsing the recipes.

The issue did not occur if the order of the layers in config.yaml is different:

No-crashes for:

 - foo
 - bar
 - basement

 - basement
 - foo
 - bar

Backtrace

An internal Exception has occured. This should not have happenend.
Please open an issue at https://github.com/BobBuildTool/bob with the following backtrace:
Bob version 0.25.0
Traceback (most recent call last):
  File "/home/hubert/bob_venv/lib/python3.12/site-packages/bob/scripts.py", line 152, in catchErrors
    ret = fun(*args, **kwargs)
          ^^^^^^^^^^^^^^^^^^^^
  File "/home/hubert/bob_venv/lib/python3.12/site-packages/bob/scripts.py", line 261, in cmd
    ret = cmd(args.args, bobRoot)
          ^^^^^^^^^^^^^^^^^^^^^^^
  File "/home/hubert/bob_venv/lib/python3.12/site-packages/bob/scripts.py", line 59, in __ls
    doLS(*args, **kwargs)
  File "/home/hubert/bob_venv/lib/python3.12/site-packages/bob/cmds/misc.py", line 107, in doLS
    recipes.parse(defines)
  File "/home/hubert/bob_venv/lib/python3.12/site-packages/bob/input.py", line 3506, in parse
    self.__parse(envOverrides, platform, recipesRoot)
  File "/home/hubert/bob_venv/lib/python3.12/site-packages/bob/input.py", line 3557, in __parse
    recipe.resolveClasses(recipeEnv)
  File "/home/hubert/bob_venv/lib/python3.12/site-packages/bob/input.py", line 2208, in resolveClasses
    p.inherit(cls.__properties[n])
              ~~~~~~~~~~~~~~~~^^^
KeyError: 'Config'

repocase.tar.gz

[icedieler]

I can reproduce the same bug. Reordering the layers then has other side effects that e.g. m4 tools are found missing.

[jkloetzke]

This was fixed already by #603 (d08ac37 to be precise).

The missing m4 tool is most probably related to the updates of BobBuildTool/basement#247. You will probably have to pull the basement layer. If the problem persists, we should track the issue separately over there.

[rhubert]

Thanks - I can confirm that the error is not raised using master...