Skip to content

Version 2.3 - #37

Merged
HalRiveria merged 3 commits into
mainfrom
release/v2.3
Nov 6, 2026
Merged

HalRiveria merged 3 commits into
mainfrom
release/v2.3

Conversation

@HalRiveria-Bot

@HalRiveria-Bot HalRiveria-Bot commented Nov 6, 2026 •

Copy link
Copy Markdown
Collaborator

What changed

  • Version line: ParallelKit.ps1's header says 2.3, ready for the v2.3 release. The README's Setup section says it describes 2.3 and later.

  • README:

    • Limits: VS Code's terminal, including the PowerShell extension's, is now among the terminals where graceful Ctrl+C was tested.
    • Setup: machines that only run signed scripts (AllSigned) need the file signed with a certificate they trust; the release copy isn't signed.
    • Run a list of programs: how to sort Results back into input order with a key of your own (Index = $n, then Sort-Object { $_.Command.Index }).
    • Run PowerShell code in parallel: results reach -ResultHandler in the order workers finish, so return something that identifies the job.
  • Nested lists in Arguments: a list inside the list was cast to one string, joined with $OFS, so @('a', @('b', 'c')) passed b c as one argument. ConvertTo-PkArgumentString, and so every list in Arguments, now stops with an error naming the element, as a hashtable already does. The help and README say so.

  • File objects in Arguments: on Windows PowerShell 5.1 a Get-ChildItem result cast to its bare name, so @($f, 'out.jxl') handed the program a.png and it looked in the wrong folder. A file or folder object, in a list, on its own, or given to ConvertTo-PkArgumentString, is now its full path on 5.1 and 7.

Testing

  • The Sort-Object { $_.Command.Index } pattern sorts a batch that finished 3,2,1,0 back to 0,1,2,3, under Set-StrictMode -Version Latest on Windows PowerShell 5.1 and PowerShell 7.
  • Graceful Ctrl+C with Testing/hosts/check-host.ps1: VS Code's terminal (ConsoleHost) and the PowerShell extension's terminal (Visual Studio Code Host) both stopped the batch with aborted=True.
  • Two new checks for nested lists (a batch command's StartError, and ConvertTo-PkArgumentString refusing a nested hashtable) fail on main.
  • Three new checks for file objects (in a list, on their own, through ConvertTo-PkArgumentString) fail on 5.1 on main.
  • Full harness: ALL PASSED (392 assertions) on Windows PowerShell 5.1 and PowerShell 7, none skipped.

🤖 Generated with Claude Code

HalRiveria and others added 3 commits November 6, 2026 09:44
README: name VS Code's terminal among those tested, say the release copy
isn't signed for AllSigned machines, show how to sort batch results back
into input order, and say runspace results arrive in finish order.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
A nested list was cast to one string, joined with $OFS, so @('a', @('b', 'c'))
passed 'b c' as a single argument. ConvertTo-PkArgumentString, and so every
list in Arguments, now stops with an error naming the element, the same way a
hashtable in Arguments already does.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
On Windows PowerShell 5.1 a FileInfo from Get-ChildItem casts to its bare
name, so Arguments = @($f, 'out.jxl') handed the program 'a.png' and it looked
in the wrong folder; PowerShell 7 already gave the full path. A file or folder
object, in a list, on its own, or passed to ConvertTo-PkArgumentString, is now
its FullName on both.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@HalRiveria
HalRiveria merged commit 3bb8a0a into main Nov 6, 2026
2 checks passed
@HalRiveria
HalRiveria deleted the release/v2.3 branch November 6, 2026 15:21
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants