Job results (from Receive-Job) are grouped by output type, differently than "normal" (BackgroundJob) jobs
还没有人认领这个 Issue。
评估
- 难度
- 4/5
- 预计耗时
- 3-5 天
- 新手友好度
- 35/100
- Issue 类型
- 缺陷
- 描述清晰度
- 描述清楚
- 活跃度
- 停滞
- 技术栈
- powershell
- 领域
- backend
调研方向
The issue shows the behavior with Start-ThreadJob and Receive-Job on PowerShell 7.4.5 and ThreadJob 2.1.0. Start by reproducing the example and comparing its output order with Start-Job. Trace how ThreadJob collects and exposes the different output streams; done means Receive-Job preserves the order of interleaved output types.
由索引模型根据 Issue 内容生成。
描述
Consider the following code which starts a ThreadJob:
$job = Start-ThreadJob -ScriptBlock {
for( $i = 0 ; $i -lt 100 ; $i++ )
{
Write-Output "output $i"
Write-Host "host output $i"
Write-Information "info output $i"
Write-Verbose "verbose output $i"
Write-Warning "warning output $i"
Start-Sleep -Seconds 5
}
}
If I receive results of the job, the output is grouped according to the type of output:
PS C:\Users\me> Receive-Job $job
output 0
output 1
output 2
WARNING: warning output 0
WARNING: warning output 1
WARNING: warning output 2
host output 0
host output 1
host output 2
PS C:\Users\me>
This is in contrast to “normal” jobs—if I switch the call out for Start-Job, the results come in a more expected order:
PS C:\Users\me> Receive-Job $job
output 0
host output 0
WARNING: warning output 0
output 1
host output 1
WARNING: warning output 1
output 2
host output 2
WARNING: warning output 2
PS C:\Users\me>
Expected behavior
I expect the output from Receive-Job of a ThreadJob to come in the same order as from a BackgroundJob.
This is because I expect to be able to use thread jobs as a "drop-in" replacement for background jobs (modulo restrictions imposed due to running in the same process, like of course you wouldn't be able to load different versions of .NET assemblies).
Actual behavior
The output from a ThreadJob is all grouped by output type (all Warnings grouped together, all host output grouped together, etc.).
Environment data
Name Value
---- -----
PSVersion 7.4.5
PSEdition Core
GitCommitId 7.4.5
OS Microsoft Windows 10.0.26290
Platform Win32NT
PSCompatibleVersions {1.0, 2.0, 3.0, 4.0…}
PSRemotingProtocolVersion 2.3
SerializationVersion 1.1.0.1
WSManStackVersion 3.0
PS C:\Users\me> gmo *thread*
ModuleType Version PreRelease Name ExportedCommands
---------- ------- ---------- ---- ----------------
Binary 2.1.0 Microsoft.PowerShell.ThreadJob Start-ThreadJob
Version
7.4.5 / 2.1.0
- 主要语言
- PowerShell
- 星标
- 37
- 派生
- 22
- PR 合并指标
- 30 天内没有已合并 PR
环境准备
- 没有 Dockerfile 或 Docker Compose 文件
- 没有 Pull Request 模板
- 阅读贡献指南
从这里开始
- 先读完整个 Issue，再读项目的贡献指南。
- 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
- Fork 仓库，在一个分支上完成修改。
- 提交 Pull Request，并在描述里引用这个 Issue 编号。
PowerShell/ThreadJob 的其他 Issue
-
难度 4/5 3-5 天 新手友好度 48/100
PowerShell/ThreadJob#59 · 1 个 reaction ·
-
enhancement
难度 3/5 1-2 天 新手友好度 56/100
PowerShell/ThreadJob#56 · 1 个 reaction ·
-
Set alias for ThreadJob command(s)可能已有人在做 @kilasuit 于 82 天前认领。 未关闭
难度 2/5 1-3 小时 新手友好度 20/100
PowerShell/ThreadJob#45 · 1 条评论 ·
-
难度 1/5 1-3 小时 新手友好度 48/100
PowerShell/ThreadJob#44 ·
-
难度 4/5 3-5 天 新手友好度 35/100
PowerShell/ThreadJob#43 ·
查看 PowerShell/ThreadJob 的全部 Issue
相似的 Issue
-
难度 2/5 1-3 小时 新手友好度 72/100
nebari-dev/nebi#630 ·
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 78/100
router-for-me/CLIProxyAPI#7084 ·
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 83/100
speakeasy-api/openapi#284 ·
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 88/100
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 68/100
jwage/phpamqplib-messenger#159 ·