Skip to content

fix(moq): follow peers through the current Python API - #6

Open
kixelated wants to merge 1 commit into
moq/pin-66bdbb93cfrom
fix/moq-follow
Open

kixelated wants to merge 1 commit into
moq/pin-66bdbb93cfrom
fix/moq-follow

Conversation

@kixelated

@kixelated kixelated commented Oct 30, 2026 •

Copy link
Copy Markdown
Owner

The current MoQ Python SDK exposes OriginConsumer.follow() for following a peer across publisher instances. The transport still calls the removed announced_broadcast() method, so calls end before receiving peer media.

Use follow() and constrain the consumer fakes to the SDK interface, preserving availability, cancellation, and resubscription behavior. No public transport API or wire-format change.

Validation: an existing peer-consumption test fails on the removed method before the source fix; all 151 MoQ transport tests pass after it against source-built current MoQ bindings. Ruff lint and format checks pass. This is a port of the fork's unreleased MoQ integration, so it needs no additional changelog fragment.

Cloud CI cannot resolve the unchanged base requirement moq-rs>=0.6.0,<0.7: only moq-rs 0.5.1 is published. The 151 local transport tests use source-built bindings; publishing an SDK is outside this API-rename fix.

Review

GPT-6.1 Sol reviewed head da7fc17fb65602ce20167ea67399762962eceb43 locally. An additional harness review is skipped for the trivial SDK method rename: the one production call retains the following handle and awaits availability through the existing path, and the three test fixtures reject nonexistent SDK methods. The existing test fails before the fix and all 151 transport tests pass after it.

(Written by GPT-6.1 Sol)

Co-Authored-By: GPT-6.1 Sol <noreply@openai.com>
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