The first screen of a new deployment names the mistake - #30
Merged
Merged
Conversation
Found by booting the Worker against an empty database with a token that
was not a token, which is the state a judge is in ten minutes after
pressing Deploy. The first page of their deployment said:
Not ready yet.
Setup could not finish: Telegram getMe failed
An API method name, returned as a 500, to somebody who has just pasted
one of two tokens into a box and has no way to tell which one was wrong.
Pasting the business bot's token instead of the console bot's is the
likeliest mistake there is, and this screen could not tell them.
Telegram says exactly what is wrong with a token — "Unauthorized:
invalid token specified" — and that sentence was carried as far as the
error's details and printed nowhere.
A rejected token is a setting to correct, not a crash, so it goes back
the way every other bad setting on this page already does: named in
missing, with what Telegram said, with what to do about it, and 503
rather than 500. Nothing is written before the token is accepted, which
was already true and is now checked: a half configured deployment looks
set up and answers nobody.
Also verified on the same boot: an empty deployment answers /health with
"awaiting_setup" and nothing missing, and Vectorize being unreachable
during setup is a warning rather than a failure.
5 tests, RED-checked by putting the crash back. 785 pass.
Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01FMFyy3oXb9u2AxoYQKRXHu
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
1 participant
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.
Found by booting the Worker against an empty database with a token that was not a token — the state a judge is in ten minutes after pressing Deploy. The first page of their deployment said:
An API method name, returned as a 500, to somebody who has just pasted one of two tokens into a box and has no way to tell which one was wrong. Pasting the business bot's token instead of the console bot's is the likeliest mistake there is, and this screen could not tell them.
Telegram says exactly what is wrong with a token —
Unauthorized: invalid token specified— and that sentence was carried as far as the error'sdetailsand printed nowhere.A rejected token is a setting to correct, not a crash, so it goes back the way every other bad setting on this page already does: named in
missing, with what Telegram said, with what to do about it, and 503 rather than 500. It now reads:Nothing is written before the token is accepted — already true, now checked: a half-configured deployment looks set up and answers nobody.
Also verified on the same boot: an empty deployment answers
/healthwithawaiting_setupand nothing missing, and Vectorize being unreachable during setup is a warning rather than a failure.5 tests, RED-checked by putting the crash back. 785 pass.
🤖 Generated with Claude Code
https://claude.ai/code/session_01FMFyy3oXb9u2AxoYQKRXHu