Fix direct sandbox hosts for shared URLs and prepare v0.1.6 - #19
Merged
Merged
Conversation
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.
When
sandboxUrlishttps://sandbox.agentbox-runtime.ru,getSandboxDirectUrl()currently buildshttps://<port>-<id>.sandbox.agentbox-runtime.ru. That hostname does not match the configured one-label wildcard route, so browser filesystem traffic cannot reach the sandbox.Derive direct hostnames from
agentbox-runtime.ruwhen the shared endpoint issandbox.<sandboxDomain>. Keep the configured URL for header-routed requests and preserve existing custom-proxy behavior. Add a regression test for both URL forms and prepare the lockstep SDK packages for v0.1.6.Validation:
pnpm format:check,pnpm lint,pnpm typecheck,pnpm testmake go-checkmake generatetwice; generated output was stable./scripts/build-release.sh, public artifact check, release artifact installation testsThe KVM release-runtime suite remains a required gate before tagging v0.1.6. No production deployment is included in this PR.