Cannot interrupt / stop / cancel, have to SIGKILL

[bendavis78]

I found my prompt was just hanging (it's unclear what it was trying to do). You can see here the result of me pressing Ctrl+C continuously:

I had no way to stop the current prompt/request or to even exit goose. I had to send a SIGKILL from another terminal window.

[alexhancock]

I've run into this one as well recently. We will look into it and report back.

[michaelneale]

yeah - looking for a way to have it reproduce, never found one but if anyone does, then it could be solved I am sure.

[alexhancock]

Did we do something to address this? I haven't noticed it as much

cc @lifeizhou-ap who I think I remember seeing a PR from

[lifeizhou-ap]

Did we do something to address this? I haven't noticed it as much

cc @lifeizhou-ap who I think I remember seeing a PR from

HI @alexhancock ,

I merged this PR #3599 which only fixed unexpected warning/error message when running the subagent/subrecipe tasks.

@DOsinga merged this PR #3554 recently. It might fix this issue but I am not 100% sure.

If there are steps to reproduce the issue, we can test with the main branch to make sure whether the issue has been fixed .

[alexhancock]

I believe this one is resolved. Feel free to reopen if you find a way to reproduce it again.