debug_stream

Diagnose H.264 streaming client connection and chunk distribution issues in Rust code.

Updated Jan 23, 2026
One-click install
npx skills add https://github.com/c4software/hdmi-wifi-hackathon --skill debug-stream
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: debug_stream
Source: https://github.com/c4software/hdmi-wifi-hackathon/tree/main/.agent/skills/debug_stream
Command: npx skills add https://github.com/c4software/hdmi-wifi-hackathon --skill debug-stream

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill helps diagnose issues in stream distribution and client connections for the HDMI streaming server. It targets debugging scenarios where multiple clients connect, network drops, or chunk distribution fails.

Core Features & Use Cases

  • Trace client subscriptions: understand how subscribers attach to the Pub/Sub channel and how streams are delivered per request.
  • Identify bottlenecks: spot lag, dropped chunks, and header mismatches impacting video delivery.
  • Use Case: when a browser disconnects after connecting to /ws, use this skill to inspect the subscriber lifecycle and verify the broadcast channel capacity.

Quick Start

Run a curl probe to http://localhost:8080/ws and monitor the server logs to confirm a new client connection and data flow.

Frequently Asked Questions about debug_stream

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I debug a websocket client disconnecting immediately after connecting to an H.264 streaming server?

To debug websocket client disconnects in H.264 streaming servers, inspect the subscriber lifecycle in client_manager.rs and monitor server logs to verify broadcast channel capacity and detect header mismatches causing drops.

Why does my Pub/Sub streaming architecture throw Lagged errors when multiple clients connect?

Lagged errors in Pub/Sub streaming architectures occur when broadcast channel capacity is exceeded. Analyze chunk distribution paths in main.rs to identify bottlenecks and adjust channel capacity to resolve the lag.

What is the best way to trace chunk distribution failures across a websocket endpoint in a Rust streaming server?

The best way to trace chunk distribution failures across a websocket endpoint is to analyze code paths in src/main.rs and src/client_manager.rs to spot dropped chunks and verify Pub/Sub delivery per request.

Can I use this to diagnose network instability affecting H.264 video delivery in an axum streaming application?

Yes, you can diagnose network instability affecting H.264 video delivery in axum streaming applications by tracing client subscriptions and identifying bottlenecks causing dropped chunks during multi-client network drops.

How do I verify data flow when a new client subscribes to a live stream websocket?

To verify data flow for a new websocket live stream subscriber, run a curl probe to the /ws endpoint and monitor server logs to confirm the client connection and chunk delivery.