Skip to content
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

Emit disconnect_document with errorType to FRS on FF client disconnects #23958

Draft
wants to merge 68 commits into
base: main
Choose a base branch
from

Conversation

RishhiB
Copy link
Contributor

@RishhiB RishhiB commented Feb 28, 2025

Currently, when clients disconnect, no specific reason is sent to FRS, making it difficult to distinguish between normal disconnects and data corruption cases. This PR adds an event disconnect_document which will be emitted from R11sDocumentDeltaConnection to FRS if the error that is causing the disconnect is a FluidErrorTypes.dataCorruptionError

Changes made

  1. Add a disconnect_document event emission in R11sDocumentDeltaConnection when disconnecting

  2. Capturing error details including:

    • Client ID
    • Document ID
    • Error type
    • Corruption status (based on error type)
  3. Adding a server-side handler in the Nexus lambda to log these disconnection events via Lumberjack, anything beyond this is out of scope of this PR

AB#13598

This is a copy of #23550 with Jason's feedback

@RishhiB RishhiB requested review from Copilot and jason-ha and removed request for Copilot February 28, 2025 21:50
@github-actions github-actions bot added base: main PRs targeted against main branch area: driver Driver related issues area: server Server related issues (routerlicious) labels Feb 28, 2025
@github-actions github-actions bot removed the area: server Server related issues (routerlicious) label Feb 28, 2025
@RishhiB RishhiB marked this pull request as draft March 3, 2025 17:54
Copy link
Contributor

@jason-ha jason-ha left a comment

Choose a reason for hiding this comment

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

LMK when actually ready for review (build failed and not showing all of the changes)
Should probably clone the outstanding issues from the prior PR and add those folks to PR.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area: driver Driver related issues base: main PRs targeted against main branch
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants