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

fix: handle double write of same data #613

Merged
merged 1 commit into from
Nov 21, 2024
Merged

fix: handle double write of same data #613

merged 1 commit into from
Nov 21, 2024

Conversation

nathanielc
Copy link
Collaborator

Prior to this change a write of the same data (keyed by the event id) would cause an error the batching logic of the write path. It was assumed that double writes would not happen and so the channel to report the insert result was dropped, causing an error.

Now all channels are preserved and the result is sent to all.

Prior to this change a write of the same data (keyed by the event id)
would cause an error the batching logic of the write path. It was
assumed that double writes would not happen and so the channel to report
the insert result was dropped, causing an error.

Now all channels are preserved and the result is sent to all.
@nathanielc nathanielc requested review from a team and dav1do as code owners November 20, 2024 19:29
@nathanielc nathanielc requested review from smrz2001 and removed request for a team November 20, 2024 19:29
Copy link
Collaborator

@smrz2001 smrz2001 left a comment

Choose a reason for hiding this comment

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

LGTM!

🚢

@nathanielc nathanielc added this pull request to the merge queue Nov 21, 2024
Merged via the queue into main with commit 7160752 Nov 21, 2024
5 checks passed
@nathanielc nathanielc deleted the fix/double-write branch November 21, 2024 15:53
@smrz2001 smrz2001 mentioned this pull request Nov 25, 2024
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.

2 participants