Fix EF double-write in InterviewSessionRepository#14
Open
KhawarHabibKhan wants to merge 1 commit intoAzure-Samples:mainfrom
Open
Fix EF double-write in InterviewSessionRepository#14KhawarHabibKhan wants to merge 1 commit intoAzure-Samples:mainfrom
KhawarHabibKhan wants to merge 1 commit intoAzure-Samples:mainfrom
Conversation
Author
|
@microsoft-github-policy-service agree |
KhawarHabibKhan
commented
Mar 14, 2026
Author
KhawarHabibKhan
left a comment
There was a problem hiding this comment.
please review the changes.
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Fixes the double-write anti-pattern in InterviewSessionRepository where both ExecuteUpdateAsync and SaveChangesAsync are called on the same entity, causing two database round-trips and a race condition window for concurrent modifications.
Also fixes a related issue where the transcript StringBuilder logic produced leading whitespace/blank lines on the first update.
What Changed