Extract shared durable local-emulation kernel#2496
Draft
GarrettBeatty wants to merge 1 commit into
Draft
Conversation
This was referenced Jul 23, 2026
The durable-execution checkpoint state machine and in-memory operation store live in Amazon.Lambda.DurableExecution.Testing today and are hand-forked into the Lambda Test Tool's durable emulator, so the two can silently drift on replay-critical logic. Extract the shared core into a new internal package, Amazon.Lambda.DurableExecution.LocalEmulation: - InMemoryOperationStore and CheckpointProcessor (state machine, callback minting, time-skip, pending-invoke tracking) - OperationUpdateInput, a transport-neutral update record each consumer maps its own representation to at the boundary - DurableEmulationHelpers for the shared exec-0 seeding and TryGetNextResumeDelay Rewire Amazon.Lambda.DurableExecution.Testing onto the kernel: it keeps a thin SdkOperationUpdateMapper (AWSSDK OperationUpdate -> OperationUpdateInput) and drops its own processor/store. Kernel types stay internal and are shared via InternalsVisibleTo (the Test Tool grant lands with its own PR). The forked processor/store unit tests move to a new kernel test project (rewritten against OperationUpdateInput); the testing package keeps focused coverage of its SDK-update adapter. No public API or behavior change.
GarrettBeatty
force-pushed
the
feat/kernel-on-feature
branch
from
July 23, 2026 20:01
5711349 to
3d23038
Compare
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
1 participant
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.
What
Extracts the durable-execution checkpoint state machine and in-memory operation store—today duplicated between
Amazon.Lambda.DurableExecution.Testingand the Lambda Test Tool's durable emulator (a hand-maintained fork)—into a new internal package,Amazon.Lambda.DurableExecution.LocalEmulation, so the two can no longer silently drift on replay-critical logic.InMemoryOperationStoreandCheckpointProcessor(state machine, callback minting, time-skip, pending-invoke tracking)OperationUpdateInput, a transport-neutral update record each consumer maps its own representation to at the boundaryDurableEmulationHelpersfor the sharedexec-0seeding andTryGetNextResumeDelayAmazon.Lambda.DurableExecution.Testingis rewired onto the kernel: it keeps a thinSdkOperationUpdateMapper(AWSSDKOperationUpdate→OperationUpdateInput) and drops its own processor/store. Kernel types stay internal, shared viaInternalsVisibleTo. The forked processor/store unit tests move to a new kernel test project (rewritten againstOperationUpdateInput); the testing package keeps focused coverage of its SDK-update adapter.No public API or behavior change.
Stack
This is PR 1 of 2, targeting the
feature/durable-testtoolintegration branch.feat/durable-testtool-on-kernel) stacks on this and rewires the Test Tool emulator onto the kernel.Testing