Repository navigation
diag(shell): Workspace 失败打印场景阶段 (#73) - #284
Merged
Merged
Conversation
The per-tab stage stays zero for workspace-driven scenarios, so the dump now also prints the stage the workspace itself tracks.
This was referenced Oct 31, 2026
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.
内容
Workspace 的失败行补上场景自己的阶段变量：
为什么必要
三个样本的每标签页转储里
stage=0都是同一个值——那是ShellWindow::stage_，而选择/动作/复制这些场景由 Workspace 驱动，进度保存在 Workspace 的stage_里（workspace_selection_scenario.hpp用它推进 0→11 的阶段）。所以此前拿到的
stage=0不能用来判断卡在哪一步；补上这一项后，下一次命中即可知道是卡在等待标记、等待鼠标交互，还是复制阶段。验证
termforge_shell构建通过。边界
stage=保留（它对其余场景仍有效），两个 stage 分别代表不同对象，注释里已写明。Refs #73