You can clone with
call reset magic, give empty answer, the default 'n' has no affects
reset magic call core.interactiveshell.ask_yes_no with any default value,
utils.io.ask_yes_no accepts string as default answer, while core.interactiveshell.ask_yes_no pass True in!
give 'n' in reset magic, and fix the default answer of core.interactiveshell.ask_yes_no
Thanks! this particular case doesn't actually occur in master anymore (because 'n' is now given as default), but the bug still persists, even though it never comes up.
fix default value in interactiveshell.ask_yes_no
was True, should be None