Repository navigation
Deduplicate Inbox redeliveries by stable event ID - #1
Merged
Merged
Conversation
Mr444-dev
marked this pull request as ready for review
October 24, 2026 17:54
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.
Summary
EventId, backed by a PostgreSQL unique constraint.EnsureCreatedbootstrap.Verification at merge
Delivery semantics and limits
Delivery is at least once, not exactly once. The projection is a derived event summary, not authoritative workflow state. Outbox publication still holds a database transaction while waiting for Kafka acknowledgement. The Outbox DLQ does not yet have an operator-controlled replay path. This remains a portfolio prototype, not production software.
Deployment security follow-up
The HTTPS-only example Gateway and readiness probe are included. If either old database credential was ever applied to a real environment, rotate it: rewriting Git history does not revoke a credential.
History cleanup
After the merge, the public
mainand PR branch histories were rewritten. Current branch heads are:main:fbdd6f3d3c220f4702eea11b8a1aef34b0bfd283codex/idempotent-inbox-event-id:9a5ee0904a5d2747b50b8ab71e9b0651a0d812f4Local scans found no exact matches for the removed credential literals in the Git object stores of the available checkouts. GitHub may retain pull-request refs or cached views of earlier commits; consult GitHub's sensitive-data removal guidance for the remaining cleanup process.