Repository navigation
Preserve safe rejection identity through owned transaction cleanup - #46
Merged
Merged
Conversation
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.
Owners currently cannot distinguish an explicitly rejected work result from a replaced error or owned deadline after the root transaction intentionally discards the original Throwable. Add an opt-in, one-use opaque correlation key. A match is exposed only when the same private signal reaches the work, transaction and final cleanup boundaries and the original scope has acknowledged rollback, no commit or completed result boundary, complete cleanup, a current owner graph and valid original/narrowed budgets. Unsupported scopes, replacements, cancellation, expiration and uncertain cleanup remain unclassified. Existing constructors, stages, messages and behavior remain available.
Root independently replays all 124 source controls (106 retained plus 18 new), retains 104 original public/protected APIs and 97 unrelated class bytes, and checks the exact inherited lint fingerprints with zero new warnings. Two inherited diagnostics remain; this is not globally Werror-clean. Four production files and one test change; POMs, SDKs, SQL, Web dependencies and published artifacts remain unchanged. Physical PostgreSQL, LEND/HTTP adoption and full reactor CI remain separate gates.
Release policy: a later qualified release must advance the whole Jafly parent/BOM/modules/adapters/batch/published-SDK reactor together at one YY.MM.Patch. No module-only release, new counter reservation or replacement of published 26.10.23 is included. OpenPlatform must adopt the same actually published framework train through both parent and BOM.