Repository navigation
Add published DBOS cancellation and durable compensation comparison - #150
Merged
Merged
Conversation
This was referenced Oct 5, 2026
Merged
rmcdaniel
marked this pull request as ready for review
October 5, 2026 22:19
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.
Summary
Adds a reproducible comparison using published DBOS 3.2.0 and a pinned Python image for shared #136.
Three repetitions of seven supported cases distinguish callback exit, stored cancellation status and durable cleanup. The fixture uses recursive cancellation, preemptible async steps and a separately queued compensation workflow with a stable ID. It includes worker SIGKILL, fresh-worker recovery and repeated cancellation.
Async work stops without application heartbeats. A blocking step performs its late effect but does not commit a completed step. Durable cleanup steps inside the cancelled workflow are refused. A separately queued compensation workflow survives worker loss and completes. The documentation explains the application pattern and each observation's scope.
Verification
The local composition passed 21 cases with 42 cancelled parent/child workflows. Recorded results also pass the added stale-step, late-effect and fresh-worker assertions. Hosted CI will rerun the complete fixture at this PR's source identity and retain ordinary files for 90 days.
The workflow grants read-only access, pins its actions, runs without host ports, sets resource limits and removes the fixture on success or failure.
Shared #136 remains open for Durable Workflow's implementation and exact published mixed-language cascade.