Skip to content

log warning if signal messages get dropped during reconnect - #1391

Open
lukasIO wants to merge 2 commits into
mainfrom
lukas/late-reconnect-response
Open

log warning if signal messages get dropped during reconnect#1391
lukasIO wants to merge 2 commits into
mainfrom
lukas/late-reconnect-response

Conversation

@lukasIO

@lukasIO lukasIO commented Sep 2, 2026

Copy link
Copy Markdown
Contributor

No description provided.

@github-actions

github-actions Bot commented Sep 2, 2026

Copy link
Copy Markdown
Contributor

Changeset ✓

This PR includes a changeset covering all affected packages:

Package Bump
livekit patch
livekit-api patch
livekit-ffi patch
livekit-signaling patch

@lukasIO
lukasIO requested a review from ladvoc as a code owner September 2, 2026 10:23

@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 found 1 potential issue.

Devin Review

Comment on lines +1084 to +1085
let dbg = format!("{:?}", msg);
dbg.split(['(', ' ']).next().unwrap_or("Unknown").to_string()

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.

🟡 Large warnings can stall reconnection

When a dropped message is large, signal_message_variant_name formats its complete payload just to obtain the variant name. Bursts can block processing beyond the five-second deadline and force a full reconnect.

Prompt for agents
Replace the Debug-string parsing in livekit-signaling/src/lib.rs signal_message_variant_name with a bounded-cost way to identify each signal_response::Message variant without formatting nested payloads. Preserve useful variant names in the warning and add coverage for payload-heavy and scalar variants. Consider that get_reconnect_response reads from an unbounded channel under a five-second timeout, so naming a message must take constant work regardless of payload size.
Devin Review

Was this helpful? React with 👍 or 👎 to provide feedback.

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.

2 participants