Bug – Scoop: Apps containing PowerShell modules get stuck when updating (when supposedly replacing the module)

[RavenMacDaddy]

For reference, this is not a module that's part of Scoop; any apps containing PS modules, like scoop-completion, gets the corresponding data installed into the subdir modules – and apparently, while trying to replace the old version, WingetUI gets stuck in the process.

🔵 Current program set to 1665060355.9610548
🔵 Sending cancel signal...
🔵 Sending cancel signal...
🟢 Have permission to install, starting installation threads...
🟢 Waiting for install permission... title=scoop-completion, id=scoop-completion, installId=1665060452.285913
🟢 scoop installer assistant thread started for process <Popen: returncode: None args: 'powershell -Command scoop update scoop-compl...>
🔵 Current program set to 1665060452.285913
🔵 Sending cancel signal...
🔵 Sending cancel signal...

Hmm…no clue.

Log.txt

Even weirder, I don't see the output that WingetUI is getting stuck on when successfully installing the update through the CLI;

[marticliment]

what happens if you run powershell -Command scoop update scoop-completion on a command prompt window?

[RavenMacDaddy]

Here you go:

If CMD is being used in WingetUI, I suppose it ought to be updated to use PowerShell instead – but if I'm missing the point of its use, by all means educate me.

Both Winget and Scoop are optimized to be used with PowerShell, being the current CLI for the Windows OS – I'd guess the same applies for any other active package managers.

I also suppose that's why it just worked when executing directly through PowerShell (the most updated Core version to be specific), and it's a very possibly the reason for other apps failing to install as well.

I'm just waiting for updates to those specific apps – like Microsoft Edge – to show up again so that I can provide up-to-date information.

[ppvnf]

I don't know about Scoop, but Winget isn't native to PowerShell yet. See microsoft/winget-cli#221

[marticliment]

If CMD is being used in WingetUI, I suppose it ought to be updated to use PowerShell instead – but if I'm missing the point of its use, by all means educate me.

CMD is not directly used, but it is used to call a powershell instance that takes care of the scoop command. (it is python's default subprocess.Popen behaviour)

As far as I understand, the issue here is that scoop is prompting for an answer, but then (since you can't interact with the console, it gets stuck.)

I suppose this is a scoop bug, because it should take care of ran command to be unattended (as you can see, it says that the recurse parameter for whatever the function was not specified)

[marticliment]

Opened an issue on scoop, see here: ScoopInstaller/Scoop#5173

[marticliment]

Seems like it has been already fixed

[marticliment]

and they'll release the next update soon