Globber quietly fails expecting provider to handle no results #19626
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
On Windows: get-childitem \\.\INVALID0\*
Note that this is using device path syntax to a non-existing device
Expected behavior
Path not found errorActual behavior
No results, no errorError details
It looks like somewhere in the globber it's ignoring a potential error here and just validating returned results against the wildcard.Environment data
Name Value
---- -----
PSVersion 7.4.0-preview.3
PSEdition Core
GitCommitId 7.4.0-preview.3
OS Microsoft Windows 10.0.25324
Platform Win32NT
PSCompatibleVersions {1.0, 2.0, 3.0, 4.0…}
PSRemotingProtocolVersion 2.3
SerializationVersion 1.1.0.1
WSManStackVersion 3.0Visuals
No response