Expose track name and used/unused activity signals#1398
Conversation
Add `name()`, `used()`, and `unused()` to MoqTrackProducer and MoqMediaProducer so FFI consumers can observe subscriber activity. Plumb a single track accessor through moq-mux's import decoder and mirror the new API in the Python moq-lite bindings. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
|
ℹ️ Recent review info⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (4)
WalkthroughThis PR exposes track activity and naming across the MOQ producer stack. The Rust FFI layer introduces an internal 🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing Touches🧪 Generate unit tests (beta)
⚔️ Resolve merge conflicts
✨ Simplify code
Tip 💬 Introducing Slack Agent: The best way for teams to turn conversations into code.Slack Agent is built on CodeRabbit's deep understanding of your code, so your team can collaborate across the entire SDLC without losing context.
Built for teams:
One agent for your entire SDLC. Right inside Slack. Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
Add
name(),used(), andunused()to MoqTrackProducer and MoqMediaProducer so FFI consumers can observe subscriber activity. Plumb a single track accessor through moq-mux's import decoder and mirror the new API in the Python moq-lite bindings.