KeyError: 'logger' when executing a NER trainer

I just updated to the Prodigy 1.11.0, and get the following:

python3 -m prodigy train nl_party_model_20210816/ --ner poc_parties --base-model nl_core_news_sm --eval-split 0.2
ℹ Using CPU

========================= Generating Prodigy config =========================
ℹ Auto-generating config with spaCy
ℹ Using config from base model
✔ Generated training config
Traceback (most recent call last):
  File "/usr/lib/python3.7/", line 193, in _run_module_as_main
    "__main__", mod_spec)
  File "/usr/lib/python3.7/", line 85, in _run_code
    exec(code, run_globals)
  File "/home/forge/.local/lib/python3.7/site-packages/prodigy/", line 61, in <module>
    controller = recipe(*args, use_plac=True)
  File "cython_src/prodigy/core.pyx", line 325, in prodigy.core.recipe.recipe_decorator.recipe_proxy
  File "/home/forge/.local/lib/python3.7/site-packages/", line 367, in call
    cmd, result = parser.consume(arglist)
  File "/home/forge/.local/lib/python3.7/site-packages/", line 232, in consume
    return cmd, self.func(*(args + varargs + extraopts), **kwargs)
  File "/home/forge/.local/lib/python3.7/site-packages/prodigy/recipes/", line 282, in train
  File "/home/forge/.local/lib/python3.7/site-packages/prodigy/recipes/", line 171, in _train
    original_logger = config["training"]["logger"]
KeyError: 'logger'

Is there anything I can do to fix it?

1 Like

Hi! It looks like this error happens if the base config doesn't contain a logger – we already have a fix and will be releasing v1.11.1 shortly, but in the meantime, you can just comment out this section in (you can run prodigy stats to find the location of your Prodigy installation).

See this comment for more background:

Hi, thank you for your quick response! Commenting out worked and I can continue now. Thanks!

Just released v1.11.1, which should fix the underlying problem :slightly_smiling_face: