fix(orchestrator): 升级器 maxBuffer 64MB + ✗ 日志截断(实机升级误判修复) - #91
Merged
Conversation
实机验证 v0.7.0 一键升级发现:build-web.sh 构建成功(exit 0)却被判失败—— execFile 默认 1MB maxBuffer 被 vite/npm 输出超限,err 一到,stdout 即弃。 升到 64MB;同时 ✗ 日志行加 clip(),失败只留首 300 字符,不再把整段 构建输出塞进 UI 升级横幅。 另实机确认:desktop profile pnpm up 首次会撞 minimumReleaseAge 供应链 策略(依赖刚发版距窗口太近),属外部策略瞬态,重试即过,升级器不改。 验证:system-upgrade 12 套全绿;UI 实测升级链路(见 PR 描述)。
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.
背景
v0.7.0 发版后实机验证「设置 → Workflow One → 一键升级」:升级链路跑到源码重建的 build-web.sh 步骤,UI 报 ✗ 失败——但构建实际成功(手动复跑 exit 0,产物齐全)。
根因
run()用execFile默认 1MB maxBuffer;build-web.sh 的 vite + npm 输出(含 document-preview 双份 chunk 清单 + install-scripts 警告)超限。maxBuffer 超限触发 err,stdout 一并丢弃——构建明明 exit 0 也被判失败。修复
maxBuffer: 64MBclip()(首 300 字符),整段构建输出不再塞进 UI 横幅实机另证(不改代码)
desktop profile(npm 渠道)首次
pnpm up撞minimumReleaseAge供应链策略:依赖dsh-better-sidebar@0.17.1刚发版 1.2h,距策略窗口不足。属外部策略瞬态,时间窗过后重试即过(已实测 ^0.7.0 落地)。升级器对这类失败本来就支持重试,行为正确。验证