Scriptblock exceptions are not returned

The following yields no output: Start-ThreadJob {throw "foo"} | Receive-Job -Wait

If you use Start-Job instead the exception is returned as a non-terminating error. Is there any way Start-ThreadJob could do the same?

[PaulHigin]

@ajansveld Thanks for pointing this out! The reason this terminating error isn’t reported is because, unfortunately, PowerShell doesn’t currently provide a public or protected accessible way to report it as part of the job state change. I was aware of this when writing the code but neglected to include a TODO comment and mention this in the release notes. https://github.com/PaulHigin/PSThreadJob/blob/master/ThreadJob/ThreadJob/PSThreadJob.cs#L207

The only way I can see to fix this is to modify PowerShell API to provide protected class access to setting job state along with an optional exception (which would be the terminating exception). This is currently provided as internal access but derived classes such as ThreadJob cannot access the API.

I am sure we can get this change into PSCore (https://github.com/powershell/powershell) but then we would have compatibility issues with Windows PowerShell. But I guess we can have different versions of ThreadJob targeted to different versions of PowerShell.

There is another problem similar to this that I did mention in the release notes. And that is support for processing a $using: variable is also internal access to PowerShell, and so ThreadJob cannot support the using variable without first modifying PowerShell. I’ll create an issue for this as well.

[PaulHigin]

I was able to fix this by using Job2 and implementing JobSourceAdapter.