docs: make the on-chain command runnable and name the 402 - #6
Merged
Conversation
The section read "ffmpeg ... | uv run client.py --signer ...", where the ellipsis is a placeholder, so the natural move is to copy the offchain snippet above it, which carries no --signer. That fails with a 402 about a signer address the reader never set: the SDK only sends the payer address header when a signer is configured, and the orchestrator needs it to build the payment challenge. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
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.
The on-chain section read
ffmpeg ... | uv run client.py --signer ..., whereffmpeg ...is a placeholder rather than a command. The natural workaround is to copy the offchain snippet just above it, which carries no--signer, and that fails with:an error naming a header the reader never set and cannot see. The SDK only sends
Livepeer-Payer-Addresswhensigner_urlis configured (live_runner.py), and the orchestrator needs it to build the payment challenge (runnerSender,server/ai_http.go), so the flag is load-bearing rather than decorative.This spells the command out in full and says what dropping
--signerproduces, so the error is searchable.