René's URL Explorer Experiment

{"@context":"https://schema.org","@type":"DiscussionForumPosting","headline":"Pipeline stops enumerating on encountering a second AutomationNull value in the input","articleBody":"## Steps to reproduce\r\n\r\nNote: `(\u0026 {})` is used to produce AutomationNull, i.e. the `[System.Management.Automation.Internal.AutomationNull]::Value` singleton representing \"no output\" in PowerShell.\r\n\r\n```powershell\r\n$automationNull = \u0026 {}\r\n1, $automationNull, 2, $automationNull, 3, 4, 5 | ForEach-Object { $_ }  | Should -Be (1..5)\r\n```\r\n\r\n## Expected behavior\r\n\r\nThe test should pass: all non-AutomationNull values should be passed through (while the AutomationNull values in the input are apparently themselves _not_ sent through the pipeline).\r\n\r\n## Actual behavior\r\n\r\nThe test fails, because enumeration unexpectedly _stops_ on encountering the _second_  non-AutomationNull value.\r\n\r\n```none\r\nExpected @(1, 2, 3, 4, 5), but got @(1, 2).\r\n```\r\n\r\nNote that using true `$null` values does _not_ exhibit the problem: the following test succeeds:\r\n\r\n```powershell\r\n1, $null, 2, $null, 3, 4, 5 | ForEach-Object { $_ }  | Should -Be 1, $null, 2, $null, 3, 4, 5 # OK\r\n```\r\n\r\n## Environment data\r\n\r\n```none\r\nPowerShell Core 7.2.0-preview.3\r\n```\r\n","author":{"url":"https://github.com/mklement0","@type":"Person","name":"mklement0"},"datePublished":"2021-02-28T15:29:43.000Z","interactionStatistic":{"@type":"InteractionCounter","interactionType":"https://schema.org/CommentAction","userInteractionCount":3},"url":"https://github.com/14920/PowerShell/issues/14920"}