Closed ianmiell closed 7 years ago
May be related to CTRL-g problems. Interestingly challenge uses pause_point under the hood with no issues.
I think I've got this one:
the challenge acts on the pexpect_child object, but that has gone, so the pause_point fails, falling through to the challenge_check as there's no flag set.
This is the difference to the other cases. I need to do as the others do, and return, or call challenge on the NEW object.
Fixed; get the session id and call that before returning challenge.
after a replace container.