PY-87104 Use handler's own runProcessWithProgressIndicator instead of creating a second CapturingProcessRunner

CapturingProcessHandler already creates an internal CapturingProcessRunner
in its constructor, which adds a CapturingProcessAdapter listener.
Creating a new CapturingProcessRunner wrapping the same handler added a
duplicate adapter, causing incorrect process output handling.

Use the handler's runProcessWithProgressIndicator() which correctly
delegates to its internal runner.

GitOrigin-RevId: 44e0268d792b060e4b3f3a57d497100d6e424a28
This commit is contained in:
Vitaly Legchilkin
2026-02-14 17:53:23 +00:00
committed by intellij-monorepo-bot
parent 9a04d29d15
commit 7dfbb1efa0
@@ -2,7 +2,6 @@
package com.jetbrains.python.sdk.skeletons
import com.intellij.execution.process.CapturingProcessHandler
import com.intellij.execution.process.CapturingProcessRunner
import com.intellij.execution.process.ProcessOutput
import com.intellij.execution.target.TargetEnvironment
import com.intellij.execution.target.TargetEnvironmentRequest
@@ -132,7 +131,7 @@ class PyTargetsSkeletonGenerator(skeletonPath: String, pySdk: Sdk, currentFolder
listener?.let { capturingProcessHandler.addProcessListener(LineWiseProcessOutputListener.Adapter(it)) }
val indicator = ProgressManager.getInstance().progressIndicator
val result = if (indicator != null) {
CapturingProcessRunner(capturingProcessHandler).runProcess(indicator)
capturingProcessHandler.runProcessWithProgressIndicator(indicator)
}
else {
capturingProcessHandler.runProcess()