OpenEvolve v0.4.0: an edit boundary can disappear before evaluation
A trace of the frozen source shows why an explicitly enabled setting fails to reach the worker—and how a function rename can survive the restoration step.
AnalysisExpand summaryCollapse summary
OpenEvolve searches through proposed versions of an input program and evaluates them. Its edit-boundary option is meant to preserve text outside marked regions, such as a function name that callers depend on. At the captured v0.4.0 commit, the parallel controller omits that option when transferring configuration, so the worker defaults to False. One synthetic example shows the consequence and a precise diagnostic: inspect the worker's setting and check that evaluation receives both the preserved name and the permitted inner edit.