-
Notifications
You must be signed in to change notification settings - Fork 539
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
RishhiB
wants to merge
68
commits into
microsoft:main
Choose a base branch
from
RishhiB:cherry-pick-disconnectReason-loader
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.
Draft
Emit disconnect_document
with errorType
to FRS on FF client disconnects
#23958
RishhiB
wants to merge
68
commits into
microsoft:main
from
RishhiB:cherry-pick-disconnectReason-loader
Conversation
This file contains 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
Co-authored-by: Alex Villarreal <[email protected]>
jason-ha
reviewed
Mar 3, 2025
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.
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
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.
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 aFluidErrorTypes.dataCorruptionError
Changes made
Add a
disconnect_document
event emission in R11sDocumentDeltaConnection when disconnectingCapturing error details including:
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