You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When I run my daily task scheduled 'scoop update' it sometimes throws exception and outputs:
Updating Buckets...
PS>TerminatingError(ForEach-Object): "The following common parameters are not currently supported in the Parallel parameter set:
ErrorAction, WarningAction, InformationAction, PipelineVariable"
It believe it fails to update the buckets. It certainly throws an exception. I'm fairly certain it must have failed to update the buckets, since the problem goes away when running manually afterwards.
When scoop enters this erroneous state, every single nightly 'scoop update' task of mine fails, until I run it manually in a pwsh 7 console and after that it just works (for some time, maybe months). Sometimes I have seen it fail when running manually and then work when I start a new pwsh console, or maybe even just drop into a new pwsh subshell within same console window.
I have been unable to reliable reproduce it, but it has been going on for years, though previously I think with a different error-message about -Parallel not supported. Probably the difference in output is a pwsh update.
I've tried reproducing it by reverting all my buckets to previous commits, so scoop update has something to work on, but it doesn't fail by that. So I would expect it is some warning that is sometimes produced by the update script for some buckets that cause it to fail.
Additional context/output
Updating Scoop...
Updating Buckets...
PS>TerminatingError(ForEach-Object): "The following common parameters are not currently supported in the Parallel parameter set:
ErrorAction, WarningAction, InformationAction, PipelineVariable"
>> TerminatingError(ForEach-Object): "The following common parameters are not currently supported in the Parallel parameter set:
ErrorAction, WarningAction, InformationAction, PipelineVariable"
>> TerminatingError(ForEach-Object): "The following common parameters are not currently supported in the Parallel parameter set:
ErrorAction, WarningAction, InformationAction, PipelineVariable"
>> TerminatingError(ForEach-Object): "The following common parameters are not currently supported in the Parallel parameter set:
ErrorAction, WarningAction, InformationAction, PipelineVariable"
>> TerminatingError(ForEach-Object): "The following common parameters are not currently supported in the Parallel parameter set:
ErrorAction, WarningAction, InformationAction, PipelineVariable"
>> TerminatingError(ForEach-Object): "The following common parameters are not currently supported in the Parallel parameter set:
ErrorAction, WarningAction, InformationAction, PipelineVariable"
>> TerminatingError(ForEach-Object): "The following common parameters are not currently supported in the Parallel parameter set:
ErrorAction, WarningAction, InformationAction, PipelineVariable"
Failed Upgrade-Scoop
Current Behavior
When I run my daily task scheduled 'scoop update' it sometimes throws exception and outputs:
It believe it fails to update the buckets. It certainly throws an exception. I'm fairly certain it must have failed to update the buckets, since the problem goes away when running manually afterwards.
When scoop enters this erroneous state, every single nightly 'scoop update' task of mine fails, until I run it manually in a pwsh 7 console and after that it just works (for some time, maybe months). Sometimes I have seen it fail when running manually and then work when I start a new pwsh console, or maybe even just drop into a new pwsh subshell within same console window.
I have been unable to reliable reproduce it, but it has been going on for years, though previously I think with a different error-message about -Parallel not supported. Probably the difference in output is a pwsh update.
I've tried reproducing it by reverting all my buckets to previous commits, so scoop update has something to work on, but it doesn't fail by that. So I would expect it is some warning that is sometimes produced by the update script for some buckets that cause it to fail.
Additional context/output
when running
Possible Solution
See changeset #6127
Workaround for the user by wrapping scoop
A work-around for me personally may be the following, which should work as
scoop-update.ps1
does not use -Parallel unless it detects pwsh 7:The text was updated successfully, but these errors were encountered: