test(conformance): plugin hook-info field-shape handlers (10-19..10-23) - #602
Draft
wangyb-A wants to merge 4 commits into
Draft
test(conformance): plugin hook-info field-shape handlers (10-19..10-23)#602wangyb-A wants to merge 4 commits into
wangyb-A wants to merge 4 commits into
Conversation
wangyb-A
requested a deployment
to
ai-pr-review-runtime
August 6, 2026 23:55 — with
GitHub Actions
Waiting
wangyb-A
requested a deployment
to
ai-pr-review-runtime
August 6, 2026 23:55 — with
GitHub Actions
Waiting
wangyb-A
force-pushed
the
plugin-hook-field-shape
branch
from
August 10, 2026 23:44
fd7c2c6 to
0bd1029
Compare
added 4 commits
August 11, 2026 01:11
The parity fix beneath this commit exposes fields the shape handlers could not previously read. Dump them so 10-19, 10-21 and 10-22 assert the real surface rather than recording its absence: - 10-19: operationsCount and updatedOperationsCount on invocation-start, operationsCount and executionStartTimestamp on invocation-end. - 10-21: isReplay on attempt-start and attempt-end, alongside the distinct isReplayingChildren (dumped unasserted). - 10-22: attempt and isReplay on each change delta item. The handler javadocs previously documented these as missing Java surfaces; that prose is updated to describe what is now exposed and to note that payload fields remain deliberately absent.
wangyb-A
force-pushed
the
plugin-hook-field-shape
branch
from
August 11, 2026 04:34
0bd1029 to
2b28744
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
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 5 conformance handlers (
conformance-tests/src/main/java/plugin/Plugin{InvocationInfo,OperationInfo,AttemptInfo,OperationChange,ContextInfo}Shape.java) plustemplate_plugin.yamlentries implementing plugin hook-info FIELD-SHAPE requirements 10-19..10-23 from aws/aws-durable-execution-conformance-tests#72 (land that PR first).Each handler logs ONE single-line JSON record per hook event: a canonical camelCase dump of that hook's own info record, with null/unexposed fields OMITTED so a missing key fails its assertion. Real SDK APIs only, spotless-clean.
Stacked PR
Top of a 2-PR stack — base is the parity-fix branch, not
main.plugin-hook-parity-fix), exposes the missing hook-info fields.The dependency is real, not cosmetic: the final commit here dumps
operations/updatedOperations,isReplay,attempt,executionInput,executionResultand the operationresult, which only exist after the parity fix. Review the base PR first; merge it first.Testing
Live plugin conformance suite (us-west-2), run against the full stack: 23 cases, 0 failures, 2 skipped — 21/21 covered, up from 18/21.
The three prior failures were the deliberate parity signals these handlers exist to produce; the base PR resolves all three.
OperationInfo.status, subType tokens, and correctisReplayingChildrensemantics), plus the entire mapped 10-1..10-17 regression.One caveat on evidence: the runner asserts the
ExpectedLogsfield-presence probes against CloudWatch during the run and then deletes the stack, which takes the log groups with it. The passing assertions are the record; the raw emitted hook records were not retained as an artifact.Closes #604