ForEach -Parallel $pwd

Steps to reproduce

Go to some directory other then ~. Run 1 | % -Parallel {$pwd}

Expected behavior

Output should be the same as just $pwd

Actual behavior

Output is always the ~ directory.

Environment data

Name                           Value
----                           -----
PSVersion                      7.0.0-preview.3
PSEdition                      Core
GitCommitId                    7.0.0-preview.3
OS                             Darwin 18.7.0 Darwin Kernel Version 18.7.0: Tue Aug 20 16:57:14 PDT 2019; root:xnu-4903.271.2~2/RELEASE_X86_64
Platform                       Unix
PSCompatibleVersions           {1.0, 2.0, 3.0, 4.0…}
PSRemotingProtocolVersion      2.3
SerializationVersion           1.1.0.1
WSManStackVersion              3.0

[mklement0]

@PaulHigin

Making Start-ThreadJob follow Start-Job’s example generally makes sense, but note that:

(a) it already behaves differently from Start-Job

(b) even if that were to be fixed, Start-Job’s behavior is unfortunate

© Ideally, we’d have a consistent experience across all job/thread-related features, meaning:

• Start-Job
• Start-ThreadJob
• postpositional & to start a job
• ForEach-Object -Parallel

The question now is:

Can we consider Start-Job’s default-to-$HOME behavior a bug / something worth fixing as a Bucket 3: Unlikely Grey Area change, as argued by @iSazonov above?

If so, we can achieve the desired consistency, by making all features default to the caller’s current location.

I’m certainly personally in favor of that, but I haven’t looked into how likely it is that existing Start-Job code relies on $HOME to be the default directory.

[PaulHigin]

I have submitted a PR for the fix for ForEach-Object -Parallel (#10672 ).