Repository navigation
fix: 保留维护阶段记录,避免重建失败误标为停止任务 - #261
Draft
lzh2034855417-beep wants to merge 2 commits into
Draft
lzh2034855417-beep wants to merge 2 commits into
lzh2034855417-beep wants to merge 2 commits into
Conversation
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.
问题与结果
Related to #254(仅处理阶段误报部分)。重建进入数据保护等阶段后,细粒度进度会覆盖
lastStage;页面或进程恢复后无法从该文案匹配阶段,而未知阶段被夹到第 0 步,导致后续失败显示成“停止 Web 与终端任务”失败。本次保留最近已识别的维护阶段,阻止较早阶段回退,同时继续更新当前 detail。普通备份及无阶段表的恢复/回滚任务保留原来的进度行为。阶段无法识别时保留
current=-1,不虚构第一步失败、计数或 footer 半步进度。沿用现有持久化字段,没有数据复制、删除、回滚或权限操作的行为变更。验证
5958f4b5d9d8046168629e41ee43aba930d3954d;验证提交11b7583137d441a2e164d31fb8fdfada51ee3020仅额外携带云端验证 workflow。最终5ecaf558186d1a38938e9f416e3e6702872c67cf应用该运行的 7 份格式化源码,逐文件 SHA256 与回执一致,Java token 完全不变;PR 不包含临时 workflow。范围与待验收
仍依赖现有语言/模式文本匹配,未覆盖所有组合;已丢失的历史阶段不能凭空还原。此 PR 不解决 #254 的 PERMISSION_DENIED 根因、静默维护页或 pending 恢复/放弃行为,不关闭该 issue。
目前证据为相关 JVM/Robolectric 测试及静态检查,未完成全仓测试、APK 构建或真机进程重建验收,因此提交 Draft。未在本机执行 DSHA 项目代码、测试或构建。