-
Notifications
You must be signed in to change notification settings - Fork 219
feat(rtc_engine): report the reconnect reason to the server on resume #1338
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Open
xianshijing-lk
wants to merge
2
commits into
main
Choose a base branch
from
sxian/report-reconnect-reason
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
+139
−11
Open
Changes from all commits
Commits
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,14 @@ | ||
| --- | ||
| livekit: patch | ||
| livekit-api: patch | ||
| livekit-ffi: patch | ||
| livekit-uniffi: patch | ||
| --- | ||
|
|
||
| Report the reconnect reason to the server when resuming. | ||
|
|
||
| Resumes previously sent no reason, so server-side telemetry could not attribute why Rust | ||
| clients reconnect — every resume looked like `RR_UNKNOWN`. The engine now records what caused | ||
| the episode (signal disconnected, publisher failed, subscriber failed) and reports it on each | ||
| resume attempt. The v0 signalling path was also missing the `reconnect_reason` query parameter | ||
| entirely, so it would not have been reported even if a reason had been supplied. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
🟡 A published library function changes its call signature without being flagged as a breaking change
A function that outside code can call is given an extra required argument (
SignalClient::restartatlivekit-api/src/signal_client/mod.rs:307-310) while the change is described as having no public-facing impact, so anyone already calling it will find their code no longer works after upgrading.Impact: External users of the API crate hit an unexpected build break on a patch release.
Public reachability of the changed signature and the repository rule it touches
livekit-api/src/lib.rs:27exposespub mod signal_client(behind thesignal-clientfeature), andSignalClient/restartare bothpub, sorestart()is part of livekit-api's public API surface — notpub(crate)as the PR description states.AGENTS.mdrequires that breaking public API changes be avoided unless necessary and that the author be explicit about them; the changeset (.changeset/report_reconnect_reason_on_resume.md) marks livekit-api as apatch. Either keep the old zero-argument entry point (delegating withReconnectReason::RrUnknown) and add a reason-taking variant, or state the break explicitly and bump accordingly.Prompt for agents
Was this helpful? React with 👍 or 👎 to provide feedback.