Hey @dave333 and @sandbug7. I’m so sorry this ticket has gone unanswered for so long.
We have a team assigned to help resolve the stuck process issue and to complete the addition of 7.3. They’re actively working on these items and we expect an update in weeks, not months.
We’ve also made sure to dedicate additional resources to ensure more prompt maintenance & .org support ticket responses for PHP COMP in the future.
In the mean time, we’re focusing on fixing the cases of runaway processes as well as adding 7.3 in order to get a release out as soon as possible. Sorry again for the trouble.
As a reminder… It’s best to run PHP COMP in a development or non-production environment so that you do not introduce the load of code scanning on your production environment (stuck process or no). Of course, as a ~linting tool PHP COMP is purpose built to be used to vet code before pushing live.
I’m guessing you all likely know that, but I wanted to note it for the thread.
If you have any other questions, please let me know!
