FlexMeasures / flexmeasures / 29336072009

82%

push

github

fix: guard against missing 'name' key when scanning scheduler result dicts (#2313)

trigger_and_get_next_schedule's post-processing loop used result["name"]
(unguarded) right after result.get("name") on the line above, for the
"commitment_costs" check. Schedulers whose result dicts don't carry a
"name" key at all - e.g. CommunityScheduler, which only returns
{"sensor": ..., "data": ...} entries - hit a bare KeyError here,
surfacing as an opaque "Scheduling job failed with str: 'name'" via the
API. Use .get() consistently.

Found while running a FLEXED community simulation against the
soc-value-at-end merge.



Claude-Session: https://claude.ai/code/session_01LQFkeGxDwErydUV5ZmHmki


Claude-Session: https://claude.ai/code/session_01LQFkeGxDwErydUV5ZmHmki

Signed-off-by: F.N. Claessen <felix@seita.nl>
Co-authored-by: Claude Opus 4.8 <noreply@anthropic.com>

1 of 1 new or added line in 1 file covered. (100.0%)

14538 of 17842 relevant lines covered (81.48%)

0.81 hits per line