cabal-install head ignores sigint (ctr+c) but responds to sigsusp (ctrl+z), sometimes (don't have a reproducable test case yet)

[cartazio]

i'm testing out using cabal-install head (head as of now, so hash 2f32275) sandboxing, and i've had an instance of ctrl+c not killing cabal in a sandboxed build, but ctrl+z suspending it correctly

(still trying to figure out how to reproduce this problem though, so this may be a useless ticket if i cant reproduce )

[23Skidoo]

Probably happens when we're reinstalling dependencies. This is the same behaviour that cabal-install has (#971).

[dcoutts]

It may also be due to the fact that we're using System.Process API that does not do let us do ctl-c handling correctly yet. The old System.Cmd.system did this right, but that feature has been hard to expose with the more flexible System.Process API. There's a ghc ticket on this if someone wants to work on it.

[23Skidoo]

I wonder whether this has been fixed by #1448.

[gracjan]

Yes, #1448 strikes again. This is super annoying. How come that it returned?

[jsl]

I just tested this issue with Cabal 1.22.0. Results:

• Ctrl-C does kill cabal install --only-dependencies --enable-tests, so that is working correctly
• Ctrl-C does kill cabal build, so that is working correctly

@gracjan I responded to your comment on #1448. It would help to get some more info on that ticket since I can't reproduce the issue you mentioned with a current cabal.

In the meantime, @cartazio it seems like the issue in this ticket has probably been resolved, since I can kill cabal with Ctrl-C during builds and installs on a recent version. Would you mind closing this ticket unless this is something you're still experiencing?

Thanks a lot!

[23Skidoo]

It likely depends on the version of process cabal-install was compiled with. Old versions don't have the delegate_ctlc feature, but we still support them.

[23Skidoo]

Optimistically closing.