You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
mkconcore accepts spaces in node/edge names, then the generated build script breaks #709
A node or edge name with a space (e.g. "PID Controller:pid.py" or an edge "my edge") is accepted by mkconcore, which exits 0. The generated build script is unquoted, so it splits the name: it creates directories "my" and "ctrl", and then fails with "cp: target 'ctrl/a.py': No such file or directory". ./build itself also exits 0, so nothing tells the user the study is broken.
Names with # or {} work; shell metacharacters like ; $ ( ) are already rejected by safe_name(). Space is the gap.
Proposal: reject spaces in node and edge names in safe_name() with a hint ("use '_' instead"). Paths (output directory) are unaffected. No sample workflow in the repo uses spaces in names. I have a fix and tests ready.
Activity