fix(templates): the terminal was not the whole of that refusal - #124
Merged
Conversation
v0.19.2 said `Missing configuration` meant the install container had a terminal, and told operators to update their node. An installation on a node already carrying that fix — daemon 0.19.2, `TERM` unset in the container, verified — refused its first call with exactly that message and downloaded all 6.87 GB on the second. So the message sent people to check a version that was already right, and that is the worst kind of diagnosis: precise, confident, and pointing away from the fix. It now names both causes and says which one a retry can get past. The tty finding stands as measured — seven failures out of seven with one, three successes out of three without, and a warm-up `+quit` beforehand does not help — and `Tty: false` stays. What was wrong was treating a cause found first as the only one. Nothing else changes: the retry that carried this installation through was already there, and this is what it was for. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01ReX2JSG6VKYShanE1F69KP
aaldersondev
force-pushed
the
fix/steam-cold-call
branch
from
August 25, 2026 14:08
17e29b3 to
bf421f7
Compare
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.
What happened
v0.19.2 shipped a diagnosis saying
Missing configurationmeans the install container had a terminal, and telling the operator to update their node.An installation then ran on a node already carrying that fix — daemon 0.19.2, commit
a9faf43,TERMunset inside the container — and its first attempt refused with exactly that message. The second downloaded all 6.87 GB and the server installed.So the message sent somebody to check a version that was already right. That is the worst kind of diagnosis: precise, confident, and pointing away from the fix.
What was actually measured, and what was assumed
Measured, and it stands: a terminal fails every time — seven out of seven with one, three out of three without, interleaved so neither time nor a Steam outage explains it. A warm-up
+quitbefore the real call does not help, and no redirection inside the script escapes it.Tty: falsestays.Assumed, and wrong: that a cause found first was the only one. With no terminal at all, a cold SteamCMD still refuses its first call now and then — twice in the runs watched, once on the node above.
What changes
Only what the script says when it gives up:
The comment above the retry loop and
docs/templates.mdcarry the same correction, and the daemon's own docblock no longer claims that line decides whether Steam installs at all — it takes down a wall, and the retry handles what is left standing.The retry that carried the installation through was already there. This is what it was for.
🤖 Generated with Claude Code