Skip to content

Media-path subscribe errors must not fail the session; clear stale dock errors - #171

Merged
iamfatness merged 1 commit into
mac-portfrom
mac-port-mac
Aug 2, 2026
Merged

Media-path subscribe errors must not fail the session; clear stale dock errors#171
iamfatness merged 1 commit into
mac-portfrom
mac-port-mac

Conversation

@iamfatness

Copy link
Copy Markdown
Owner

Two operator-facing fixes found in live testing:

  • video_subscribe_failed fell through to the generic error tail and invoked the join-failure/reconnect machinery, flipping a healthy in-meeting session to "Connection failed". It is now handled as a media-path error. When the bound participant is not in the roster (stale id persisted in source settings — Zoom mints user ids per join) it is a quiet waiting state with the recovery loop retrying; when the participant is present the error stays loud. Meeting state is never touched.
  • A successful join now clears last_error, so the dock no longer shows a previous attempt's failure banner over a live meeting.

🤖 Generated with Claude Code

…rrors

A video_subscribe_failed event fell through to the generic error tail, which
calls on_join_failed - so one media-path error flipped a healthy in-meeting
session to "Connection failed". Sources persist their participant binding but
Zoom mints user ids per join, so after a rejoin the saved id often refers to
nobody and every recovery retry raised another error dialog.

Video subscribe failures are now media-path errors like shm_create_failed:
if the bound participant is absent from the roster this is a waiting state
(log only, recovery keeps retrying quietly until they appear); if present the
error stays loud. Either way the meeting state and reconnect machinery are
untouched. A successful join also clears last_error so the dock stops
showing a dead attempt's failure over a live meeting.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
@iamfatness
iamfatness merged commit f5b8a0e into mac-port Aug 2, 2026
4 checks passed
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.

1 participant