Repository navigation
fix(server): avoid uresourced loops in Linux service units - #25185
maria-rcks wants to merge 2 commits into
Conversation
ApprovabilityVerdict: Needs Human Approval Macroscope's review found this PR requires human approval — Removing ManagedOOMPreference=avoid restores systemd's default OOM preference to address reported uresourced CPU loops. Human review is needed for this Linux service-default change and its memory-pressure availability tradeoff. You can add or adjust custom eligibility rules. Learn more. |
Thread transfer impact✅ Thread transfer remains within every enforced ceiling.
Other scenariosAll 64 scenario measurements match All 64 scenario measurements
Baseline: Scenario and decoded snapshot size10 historical turns, 5 command tools per turn, 878.9 KiB retained MCP result per historical turn, and a 1.05 MiB retained result in the measured turn.
Updated in place by a trusted workflow. PR artifacts are strictly validated and never executed. |
|
No actionable comments were generated in the recent review. Walkthrough
Merge Risk:
|
|
Note Written by Verified in a real dev environmentVerified unchanged head
Full service command transcript No code changes were needed. Verification services were stopped and the temporary systemd unit was uninstalled. Not verified
|
Co-authored-by: Yukun Shan <[email protected]>
3f1a472 to
09a6216
Compare
# Conflicts: # apps/server/src/cloud/bootService.test.ts
|
The automated pipeline stopped on this pull request and will not merge it: the capture step could not show the problem on the base commit, so there is nothing to prove fixed. Read the scenario documentation, fetched the requested commits, created the head worktree, computed the merge-base, inspected the service-unit change, and checked the operating system, systemd user manager, and uresourced availability. Uploaded the inspected environment transcript and its driver. Removed the worktree and scratch directory. It stays open for a person to finish or close. |

Linux service units emit
ManagedOOMPreference=avoid, which triggers the reported uresourced 0.5.4 CPU loop on affected Fedora/GNOME systems (#20931).The directive and its obsolete comment are removed, restoring systemd's default OOM preference.
OOMPolicy=continue, the CPU and IO weights, and agent isolation stay. Existing installations pick up the new unit on the nextt3 service install.The existing install test failed on main because the written unit contained
ManagedOOMPreference=and passes with the fix; the rendered unit also passedsystemd-analyze verify. Unverified: live Fedora/GNOME/uresourced behavior and memory-pressure handling. Human review of the changed Linux service default is still needed.Replaces https://git.cafe/pingdotgg/t3code/pulls/20968, with thanks to @nateEc for the original implementation.
Built with GPT-6.1-Sol in the Codex harness on T3 Code, reviewed by Claude Opus 5.5 in Claude Code.
Fixes #20931