Skip to content

[INFRA-19] Keep a stream host path prefix on voice origin calls - #96

Merged
rbehal merged 1 commit into
mainfrom
rahul-INFRA-19
Oct 28, 2026
Merged

rbehal merged 1 commit into
mainfrom
rahul-INFRA-19

Conversation

@rbehal

@rbehal rbehal commented Oct 28, 2026 •

Copy link
Copy Markdown
Contributor

Summary

In Gumloop sandboxes the SDK will reach the stream host through the orchestrator's credential proxy, at GUMLOOP_STREAM_BASE_URL=http://192.0.2.1/bound/gumloop-ws/api/v1. Voice session start and end use post_to_stream_host(origin=True), which replaced the whole base path with /gummies/.... That dropped /bound/gumloop-ws, so those calls would land on the proxy's API and get a 404.

origin=True now strips only a trailing /api/v1 and keeps any prefix mounted above it. Otherwise nothing changes: https://ws.gumloop.com/api/v1 still resolves to the host root, and a custom base like /custom/v2 still resolves to the root, as the existing test expects.

The sandbox template pins gumloop==0.5.6; it needs a release with this fix and a template bump before the backend turns on the proxy for SDK calls.

Part of INFRA-19

Test plan

  • New test_voice_keeps_a_path_prefix_mounted_above_api_v1 (sync and async).
  • scripts/check: ruff format, ruff, pyright, uv lock check, and pytest (872 passed; the 19 errors are tests/integration/test_live.py, which needs live credentials).

Raised from ws-rbehal

Made with Cursor


View with [code]smith Autofix with [code]smith
Need help on this PR? Tag @codesmith-bot with what you need.


Devin Review

Co-authored-by: Cursor <cursoragent@cursor.com>

@devin-ai-integration devin-ai-integration Bot left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

✅ Devin Review: No Issues Found

Devin Review analyzed this PR and found no bugs or issues to report.

Devin Review

@rbehal
rbehal merged commit eb0ccf7 into main Oct 28, 2026
10 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant