debugging troubles

[LuckyFalkor]

i am having troubles debugging my code when using your split-pipeline.
sometimes when i mistakenly think it's good to go and part way into processing a very large data set, i find myself needing to ctrl-c the operation to try a different edit of my script. except doing so seems to lock up the script and i have to close powershell.
is there anyway to allow it to exit more gracefully? perhaps intercept the ctrl-c input and tell your cmdlet to stop making new jobs so the script can close?

[nightroman]

True, I did not think of or test this sort of scenario with Ctrl-C. If you have a "small" test script for reproducing the problem this would be great and save some time. If not then I will try to build a problem case on my own.

In any case I will take a look and think of how to improve. Thank you for reporting this issue.

[nightroman]

I took a quick look. So far I cannot reproduce the issue. Ctrl-C stops some long running jobs just fine. If you do not have a test sample with a clear problem could you please at least describe your parallel jobs in more details?

In other words, the problem may be in jobs, too, not necessarily in Split-Pipeline.

Also, what are the Split-Pipeline parameters that you use (with or without a script itself)? PowerShell version? .NET version?

[LuckyFalkor]

this uses the quest activeRoles snapin
$users variable is populated with usernames from a CSV file.
i have a quad core CPU so i set count to 4
my $users file has 3500 some user names in it
i hit ctrl-c and i am never brought back to the prompt.

$users | Split-Pipeline {process{
$tempList = @()
$user = Get-QADUser -Identity $.Username
$ | Add-Member -NotePropertyName "location" -NotePropertyValue $user.Office
$_ | Add-Member -NotePropertyName "location2" -NotePropertyValue $user.Description
$_.Username
}} -Count 4 -Load 1,10 -Variable $x -Begin {Add-PSSnapin Quest.ActiveRoles.ADManagement -ErrorAction SilentlyContinue}}

[LuckyFalkor]

cleaned up my code and got rid of the quest dependency, to help thing along.
i still get the issue with this edit, fyi.
it may be important to know that i am using powershell v4

Split-Pipeline {process{
$user = Get-ADUser -Identity $.Username -Properties "Office","Description"
$ | Add-Member -NotePropertyName "location" -NotePropertyValue $user.Office
$_ | Add-Member -NotePropertyName "location2" -NotePropertyValue $user.Description
}} -Count 4 -Load 1,10}

[nightroman]

Thank you, this is all very useful (though it is unlikely that I am able to repeat this exactly). Also, I do not have PS V4 yet, if this matters. But I will think and work on this in any case.

One more silly but fair question. If you do the same/similar without Split-Pipeline (i.e. with a regular not parallel pipeline) -- can you stop it by Ctrl-C?

[LuckyFalkor]

ran this and could ctrl-c out just fine:
$users | % ` {
$user = Get-ADUser -Identity $.Username -Properties "Office","Description"
$ | Add-Member -NotePropertyName "location" -NotePropertyValue $user.Office
$_ | Add-Member -NotePropertyName "location2" -NotePropertyValue $user.Description
$_.username
}

[nightroman]

I cannot recreate your use case exactly. But I have built my own problem case,
exotic, not practical, but it shows a similar issue.

Some change fixed my problem case. I am not sure about yours. Could you
please try this test version SplitPipeline.zip from <removed>?

Let me know the results. Even if it works please do not use it in production.
It's only for checking that I am on the right track.

[nightroman]

Did you have a chance to try the proposed test version?

[LuckyFalkor]

i finally got around to testing your test version.
it worked like a charm and just to make sure it wasn't something else, i reverted back and test again and still the same issue from before.
whatever changes you made, it worked. :)

[nightroman]

Good news! I'll put this change in order then and release it soon. Thank you once again.

[nightroman]

Done, v1.2.1