Repository navigation
Conversation
…L as well The deploy tooling, the dev pod and the docs set SVO_ADAPTER_PUBLIC_URL, but the settings field is public_base_url, which pydantic-settings maps to SVO_ADAPTER_PUBLIC_BASE_URL. The value was therefore never read: run signals were silently unconfigured on the dev pod, and the token keeper's startup validation refused to start the pod once it was enabled (2026-11-03). Accept both names, deploy spelling first, and name both in the validation error. The pod was restored by also setting SVO_ADAPTER_PUBLIC_BASE_URL.
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
This branch was successfully deployed
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.
Why
Enabling the token keeper on the dev pod (#377) made the pod fail startup validation with
SVO_ADAPTER_PUBLIC_URL is empty, although the pod has that variable set. The settings field ispublic_base_url, which pydantic-settings maps toSVO_ADAPTER_PUBLIC_BASE_URL; the deploy tooling, docs and pod useSVO_ADAPTER_PUBLIC_URL. So the value was never read, which also means run signals (#375) were silently unconfigured on the dev pod until now.What
Settings.public_base_urlaccepts bothSVO_ADAPTER_PUBLIC_URL(deploy spelling, wins) andSVO_ADAPTER_PUBLIC_BASE_URL.tests/test_config_public_url.py.The dev pod was restored immediately by also setting
SVO_ADAPTER_PUBLIC_BASE_URL; after this merges either name works. Verified live after the restore:/healthok,POST /runs/{id}/tokenandPOST /runs/{id}/signalboth answer the uniform 401 for a bogus credential, i.e. signals and the keeper are configured.🤖 Generated with Claude Code