Repository navigation
diag(ime): 报告已序列化检查点 (#40) - #278
Merged
Merged
Conversation
The worker now records report/emitted after the last ConvertTo-Json and an explicit stdout flush, separating a stalled pipe from a stalled worker.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
内容
按 #40 的下一步观测,在 PowerShell 夹具最终序列化之后补一个检查点:
(同时显式
Flush()标准输出,确保这一行本身不会停留在缓冲区。)为什么
现有 9 个阶段检查点都止于
worker-returned;样本显示夹具在 2.169 s 内走完全部阶段,随后仍有约 7.9 s 无法解释。补上report/emitted后,下一次超时即可判定:报告是否已经写出。report=emitted→ 问题在"写出之后"(管道/父进程读取);验证
python -m unittest research.ime.test_hosted_inventory→ 29 tests OK(含检查点序列断言)。边界
progress.json,仍可能受同一管道停顿影响,因此它证明的是"走到了这一步",不是"父进程收到了报告"。Refs #40