Symplify: [ECS] Can't abort with Ctrl+C

[enumag]

I'm not sure when this started (I think it worked fine in the past) but now I'm unable to use Ctrl+C to abort ECS when it's running. It seems to ignore the signal. Does the same problem occur for you?

[TomasVotruba]

Never happened to me. What's the --debug/-vvv output before it stops?

How OS can influence this?

When do you have the need to abort process? Seems like DX/UX issue.

[enumag]

Never happened to me. What's the --debug/-vvv output before it stops?

Just normal [OK] No errors found. Great job - your code is shiny in style!.

How OS can influence this?

I don't know. Not an expert on signals. But I can abort composer and PHPStan just fine. On the other hand Psalm seems to have the same problem.

When do you have the need to abort process? Seems like DX/UX issue.

Right now it was when I was updating my ecs.php after migration... I fix something, run ECS then while it's running I already notice something else I need to fix by myself so I want to abort the current run, fix it and run again. No DX issue imo, just normal usage.

[enumag]

I'm using Ubuntu 18.04.

[enumag]

Ah the problem only occurs with XDebug enabled. I believe you have something in place to run ECS in a child process without XDebug when this happens, right? Well it seems this logic is broken and doesn't forward the signal as it should.

[TomasVotruba]

Yea, using xdebug with these tool is not a good idea.

How is it possible that xdebug is enabled though? We use composer xdebug handler to disable it on startup, as other tool

[enumag]

It was a bug in xdebug-handler and seems to be fixed in v1.4.3.
https://github.com/composer/xdebug-handler/releases/tag/1.4.3