Repository navigation
Fix PostgreSQL service-link lifecycle serialization recovery; beta.15 - #134
Merged
Merged
Conversation
This was referenced Oct 6, 2026
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.
Verified service-link activation could return a conflict after a genuine PostgreSQL serialization abort. Retry the complete local recipient operation at most four times, with a fresh dependency scope and DbContext on every attempt, preserving the original request, durable operation ID and current authorization. Only explicit PostgreSQL
40001is retried; business conflicts, authentication, cancellation and other database errors retain their behavior.The existing PostgreSQL lifecycle class adds two real-provider regressions for single-abort recovery and four-abort exhaustion, including rollback, same-operation recovery and exact replay. The release source version is
0.1.1-beta.15; publication follows the existing hosted release workflow after current checks pass.Validation: the ordinary solution build passed on the public head. All seven serialization cases passed locally and in the focused and whole hosted suites. The provider suite passed 218 cases with zero skips; the whole suite passed 2,075 cases with six unchanged legacy skips. All 17 original PR jobs, all 17 fresh merged-Main jobs and all nine hosted release jobs passed, including all three native archive lanes. RatelDesk 0.1.1-beta.15 is published and independently verified through anonymous downloads of all ten assets and both architecture configurations, SBOMs and provenance for all three images. Prior releases and stable/latest aliases are preserved.