fix(orch): bump envd init response_body truncation to 1024 chars#2685
fix(orch): bump envd init response_body truncation to 1024 chars#2685ValentaTomas wants to merge 1 commit into
Conversation
100 chars is enough to chop the actual errno off the end of e.g. \`failed to setup NFS volumes: failed to unmount stale NFS mount at "/workspace": ...\`, which is the exact message the Mode-A NFS-remount path logs. 1024 keeps the real cause visible without inflating log volume meaningfully — these lines fire only on init failure.
PR SummaryLow Risk Overview Reviewed by Cursor Bugbot for commit 0fdf5a6. Bugbot is set up for automated code reviews on this repo. Configure here. |
❌ 11 Tests Failed:
View the top 1 failed test(s) by shortest run time
View the full list of 22 ❄️ flaky test(s)
To view more test analytics, go to the Test Analytics Dashboard |
|
Superseded by #2700 (move envd into a dedicated network namespace), which addresses the root cause. |
|
Reopening — these are bifrost-track work, not runable. Closed by mistake. |
|
Closing — pure observability, unlikely to drive a fix going forward. The Bitfrost-era diagnostic value is already extracted; can revive if a future incident hits truncated /init response bodies again. |
Bump envd response_body truncation from 100 to 1024 chars.