-
Notifications
You must be signed in to change notification settings - Fork 8.2k
-Shuffle:$false not respected in Get-SecureRandom #26458
Copy link
Copy link
Closed
Labels
Up-for-GrabsUp-for-grabs issues are not high priorities, and may be opportunities for external contributorsUp-for-grabs issues are not high priorities, and may be opportunities for external contributors
Description
Prerequisites
- Write a descriptive title.
- Make sure you are able to repro it on the latest released version
- Search the existing issues.
- Refer to the FAQ.
- Refer to Differences between Windows PowerShell 5.1 and PowerShell.
Steps to reproduce
This is a sub-issue of #25242.
The cmdlet Get-SecureRandom does not respect explicit $false values for the -Shuffle switch parameter.
PS> $result = Get-SecureRandom -InputObject 1, 2, 3, 5, 8, 13 -Shuffle:$false
PS> $result.Count
PS> $resultExpected behavior
PS> $result = Get-SecureRandom -InputObject 1, 2, 3, 5, 8, 13 -Shuffle:$false
PS> $result.Count
1
PS> $result
5-Shuffle:$false should behave the same as omitting the -Shuffle switch, returning a single random item from the input collection.
Actual behavior
PS> $result = Get-SecureRandom -InputObject 1, 2, 3, 5, 8, 13 -Shuffle:$false
PS> $result.Count
6
PS> $result
3
13
1
8
2
5-Shuffle:$false behaves the same as -Shuffle or -Shuffle:$true, returning all items in shuffled order.
Error details
No error is thrown. The cmdlet executes but ignores the explicit $false value.
Environment data
PS> $PSVersionTable
Name Value
---- -----
PSVersion 7.5.4
PSEdition Core
GitCommitId 7.5.4
OS Microsoft Windows 10.0.26100
Platform Win32NT
PSCompatibleVersions {1.0, 2.0, 3.0, 4.0…}
PSRemotingProtocolVersion 2.3
SerializationVersion 1.1.0.1
WSManStackVersion 3.0Visuals
No response
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
Up-for-GrabsUp-for-grabs issues are not high priorities, and may be opportunities for external contributorsUp-for-grabs issues are not high priorities, and may be opportunities for external contributors