Repository navigation
Add published cancellation comparison fixtures - #148
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
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.
For cancellation #136.
Add a direct, reproducible experiment against published Restate Server1.7.13 and Python SDK1.0.5. Pin both container manifests and direct Python packages. Exercise durable parent/child/leaf cancellation, asynchronous and blocking callback exit, SIGKILL during durable cleanup and cancellation repeated during cleanup. Observe application effects separately from durable invocation status.
Three repetitions of each case. Runtime and SDK remain isolated, resource bounded, UID/GID1000, with no published host ports. Retain ordinary files, then remove the disposable stack.
The complete committed Compose reproduction at
2a384595387a5dd027f58d8a814d5e1bf127736drecords 15 cases and 45 durable invocation outcomes. Async callback exit is 21–28ms without application heartbeats. SIGKILL cleanup recovery completes in about3.014s including the three-second durable timer. Blocking callbacks run to their12s completion and perform the late effect in3/3. Another cancellation during cleanup returns202 and prevents the final compensation action in3/3, although the invocations record cancelled completion. Normal cleanup and replacement controls complete that action.Application observations and durable API records are retained as ordinary files. The disposable containers, network and scratch are removed after collection. A thin hosted job repeats the same command and retains normal Actions artifacts. Hosted checks are pending during GitHub's runner-assignment incident. This is a behavior experiment, with no overall winner or Durable Workflow release claim.