Skip to content

Handle missing debugger parameters#2707

Draft
Mirochill wants to merge 1 commit into
certtools:developfrom
Mirochill:fix-2683-debugger-missing-parameters
Draft

Handle missing debugger parameters#2707
Mirochill wants to merge 1 commit into
certtools:developfrom
Mirochill:fix-2683-debugger-missing-parameters

Conversation

@Mirochill

@Mirochill Mirochill commented May 25, 2026

Copy link
Copy Markdown

Fixes #2683

Description

BotDebugger.generate_get_runtime() injects the selected logging_level into every runtime entry before the bot starts. Sparse runtime configs can omit parameters for a bot, or set it to null, which currently raises before the debugger can continue.

This treats missing or null bot parameters as an empty mapping before adding logging_level, while preserving any existing parameters.

Tests

Not run locally.

Remote fork checks passed:

  • ReUse License Check
  • Unit tests

When BotDebugger injects a logging level into the runtime configuration, bot entries without a parameters mapping currently raise KeyError or TypeError. Treat missing or null parameters as an empty mapping so the debugger can continue with sparse runtime configs.

Add a focused regression test for missing, null, and existing parameters entries.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Bot debugger crashes when one bot has no parameters defined

1 participant