Fix #785: Atomic webhook retry increment to prevent race condition#803
Open
GhanshyamJha05 wants to merge 1 commit into
Open
Fix #785: Atomic webhook retry increment to prevent race condition#803GhanshyamJha05 wants to merge 1 commit into
GhanshyamJha05 wants to merge 1 commit into
Conversation
…condition - Add PostgreSQL function increment_webhook_retry_count with row-level locking - Replace check-then-act pattern with atomic RPC call in retry endpoint - Apply same fix to server action retryFailedWebhookEvent - Update tests to mock RPC call and test concurrent scenario - Prevents concurrent retry requests from bypassing retry limit
Contributor
|
@GhanshyamJha05 is attempting to deploy a commit to the codersogs-3057's projects Team on Vercel. A member of the Team first needs to authorize it. |
Collaborator
|
@GhanshyamJha05 |
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
2 participants
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.
fix issue #785