Skip to content

Conversation

@adamshiervani
Copy link
Contributor

In some cases, the WebRTC signalingState is slow to react, which ends up blocking the recovery of the connection.

@ym ym requested a review from Copilot April 9, 2025 21:24
Copy link
Contributor

Copilot AI left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Copilot reviewed 1 out of 1 changed files in this pull request and generated no comments.

Comments suppressed due to low confidence (3)

ui/src/routes/devices.$id.tsx:246

  • Confirm that increasing the number of reconnection attempts from 5 to 15 aligns with intended network recovery behavior without causing resource exhaustion.
reconnectAttempts: 15,

ui/src/routes/devices.$id.tsx:400

  • Ensure that removing the stable connection check does not lead to duplicate active connections; additional cleanup may be required.
if (peerConnection?.signalingState === "stable") {

ui/src/routes/devices.$id.tsx:496

  • Verify that the removal of the signalingState argument for sendWebRTCSignal does not affect the intended signaling behavior.
peerConnection?.signalingState,

@adamshiervani adamshiervani merged commit ee29cb1 into dev Apr 9, 2025
5 checks passed
ym pushed a commit to ym/jetkvm-kvm that referenced this pull request Jun 13, 2025
@IDisposable IDisposable deleted the fix/reload-on-update branch September 22, 2025 23:44
ym pushed a commit to ym/jetkvm-kvm that referenced this pull request Sep 26, 2025
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.

3 participants