source-academy / frontend / 31238729588

45%

Build Type

push

github

Committed by web-flow

Commit Message

Playground: show the Step Limit control for Python, drop the dead Execution Time one (#4260)

The "Step Limit" control (step-count based) was already wired end-to-end
into /__cse_config__ for every Conductor-based language, but its render
gate only covered js-slang's own usingSubst/usingCse/isCseVariant state,
so it silently never appeared for Python chapters even though py-slang's
CSE machine and Stepper both already read that value. Extended the gate
to also cover Conductor languages whose selected sublanguage offers a
stepper or CSE evaluator.

Removed "Execution Time" (ControlBarExecutionTime, ms-based) alongside it:
it only ever fed the legacy non-Conductor js-slang path via
originalMaxExecTime, and with conductor.enable defaulting to true for
every current chapter, that branch was already unreachable except for
SICP-JS snippets or a manually-disabled feature flag. The underlying
execTime Redux field/action is left untouched — AssessmentWorkspace and
GradingWorkspace still use it independently (question.library.execTimeMs)
for grading's own execution-timeout safety feature, unrelated to this
control.

Companion py-slang PR: the Stepper evaluator was fetching this same host
config already but discarding stepLimit, always using a hardcoded 1000.


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

Co-authored-by: Claude Sonnet 5 <noreply@anthropic.com>

Coverage Stats

3060 of 7795 branches covered (39.26%)

Branch coverage included in aggregate %.

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

3 existing lines in 2 files now uncovered.

7020 of 14536 relevant lines covered (48.29%)

30.31 hits per line