Skip to content

Recover Rip access logs quietly after Janus restarts - #302

Merged
shreeve merged 2 commits into
mainfrom
fix/access-stream-restart-recovery
Sep 11, 2026
Merged

shreeve merged 2 commits into
mainfrom
fix/access-stream-restart-recovery

Conversation

@shreeve

@shreeve shreeve commented Sep 11, 2026

Copy link
Copy Markdown
Owner

Restarting Janus drops its in-memory app registrations. Rip's access-log client retried the deleted IDs and printed every failed attempt, producing repeated socket errors and HTTP 404 diagnostics until the manager re-registered.

Stop retrying an ID after a 404 and wait for the manager to move the stream to its replacement registration. Report a repeated connection error once until a valid hello resets the diagnostic, while still reporting changed errors. Access streams and manager heartbeats share “Janus unavailable” diagnostics for known connection failures instead of Bun's misleading URL/port typo suggestion.

Validation:

  • Regression tests reproduce repeated dead-ID requests and duplicate diagnostics before the fix.
  • All 139 Rip Sites tests pass, including a real Janus restart held offline through a heartbeat, followed by app re-registration and resumed access output.
  • Language suite: 3,196 passed.
  • Browser suite: 16 passed, 2 existing skips.
  • Local app managers have been restarted to load the fix; a live Janus restart recovered all four apps.

@shreeve
shreeve merged commit 91d376f into main Sep 11, 2026
2 checks passed
@shreeve
shreeve deleted the fix/access-stream-restart-recovery branch September 11, 2026 18:37
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