I stumbled into this. Using the RUN "{file}" format of the command will hang if the {file} is missing. Then it seems its unable to do anything but hang with any additional RUNs, even if its the plain RUN command. It looks like there may be other errors (like parsing errors) that leave the environment in a broken state.
I stumbled into this late at night so I need to go back and re-test to see what the exact conditions and damages are. But I don’t want this blunder forgotten so I’m filing prematurely.
I stumbled into this. Using the `RUN "{file}"` format of the command will hang if the `{file}` is missing. Then it seems its unable to do anything but hang with any additional RUNs, even if its the plain `RUN` command. It looks like there may be other errors (like parsing errors) that leave the environment in a broken state.
I stumbled into this late at night so I need to go back and re-test to see what the exact conditions and damages are. But I don't want this _blunder_ forgotten so I'm filing prematurely.
I stumbled into this. Using the
RUN "{file}"
format of the command will hang if the{file}
is missing. Then it seems its unable to do anything but hang with any additional RUNs, even if its the plainRUN
command. It looks like there may be other errors (like parsing errors) that leave the environment in a broken state.I stumbled into this late at night so I need to go back and re-test to see what the exact conditions and damages are. But I don’t want this blunder forgotten so I’m filing prematurely.
Confirmed
RUN "missing_file.bas"
hangs and ^C leaves the system in a broken state. Seems like the only way to fix it is to exit and restart.