Skip to content

fix: task 文件大小上限 8MiB → 256MiB(修舰队自升级 SIGXFSZ) - #10

Merged
lr00rl merged 2 commits into
mainfrom
fix/taskexec-filesize-cap
Aug 12, 2026
Merged

fix: task 文件大小上限 8MiB → 256MiB(修舰队自升级 SIGXFSZ)#10
lr00rl merged 2 commits into
mainfrom
fix/taskexec-filesize-cap

Conversation

@lr00rl

@lr00rl lr00rl commented Aug 12, 2026

Copy link
Copy Markdown
Contributor

8 MiB 的 RLIMIT_FSIZE 把任务脚本能写的所有文件都限制在 8MiB 内——包括自升级时要下载的 agent 发布二进制。2026-08-12 舰队升级因此在 18/20 台节点上 SIGXFSZ(exit 153)。服务端升级脚本已改为自提权(对已部署 agent 生效);本 PR 是 agent 侧的补足,随下一版 agent 生效。256MiB 仍然挡住失控写。

lr00rl added 2 commits August 12, 2026 02:04
The 8 MiB RLIMIT_FSIZE capped every file a task script could write —
including the agent's own release binary during a self-update. The
2026-08-12 fleet upgrade died to SIGXFSZ (exit 153, 'File size limit
exceeded') on 18 of 20 attempted nodes. The server-side update script now
lifts the inherited cap itself (the only fix that reaches agents already
deployed); this raise is the belt-and-braces for non-update tasks and for
future agents once their update has run. 256 MiB still bounds runaway
writes.
govulncheck flags the sing-box stats gRPC client path under the pinned
v1.72.2. Unrelated to the rlimit change; the vuln DB entry postdates the
last release. protobuf rides to v1.36.11. Full suite green.
@lr00rl
lr00rl merged commit d2666e9 into main Aug 12, 2026
1 check passed
@lr00rl
lr00rl deleted the fix/taskexec-filesize-cap branch August 12, 2026 09:14
lr00rl added a commit that referenced this pull request Aug 17, 2026
Land the reviewed design-18 E3 node-agent work: partial chain state cannot
escape host recovery. The branch carries main's #10 task-size fix, so this
merge also reconciles the main/integration lanes. Feature commits preserved
exactly as reviewed (PR #15, CI SUCCESS on the exact head).

Constraint: Integrate only the exact PR #15 head without amending reviewed commits
Rejected: GitHub squash merge | it would destroy the reviewed Lore history
Confidence: high
Scope-risk: moderate
Reversibility: clean
Directive: Keep exact-head topology for future backports
Tested: PR #15 CI SUCCESS on exact head; gates recorded in .omx/ultragoal G002 evidence
Not-tested: Release, deployment, and fleet rollout remain out of scope
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant