Repository navigation
Don't call onPropsChanged on a child's initial render with COMPOSE_RUNTIME_SKIPPING [CLF-658] - #1592
Merged
zach-klippenstein merged 2 commits intoOct 29, 2026
Conversation
With COMPOSE_RUNTIME_SKIPPING, a child's onPropsChanged is called on its first render with old == new. The legacy runtime never does this. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
…PING composer.changed() always reports a change on first composition, so the restartable render path told WorkflowSnapshotState the props had changed even though ComposeRenderContext was just created with them. On insert, report props as unchanged and onOutput as changed instead: the snapshot state starts without an output handler, and the spurious props-changed write was what stored it. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
zach-klippenstein
marked this pull request as ready for review
October 28, 2026 23:08
zach-klippenstein
enabled auto-merge
October 28, 2026 23:11
Collaborator
Author
|
🤖 Compose runtime microbenchmarks: this PR (
Result: no measurable change.
Full resultsShallowBushyTree_ComposeNoSkip
ShallowBushyTree_ComposeSkipping
SquareishTree_ComposeNoSkip
SquareishTree_ComposeSkipping
|
tcmulcahy
approved these changes
Oct 29, 2026
zach-klippenstein
disabled auto-merge
October 29, 2026 02:20
zach-klippenstein
deleted the
zachklipp/skipping-initial-onpropschanged
branch
October 29, 2026 02:20
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.
With
RuntimeConfigOptions.COMPOSE_RUNTIME_SKIPPING, a childStatefulWorkflow'sonPropsChangedis called on its very first render withold == new. The legacy runtime andCOMPOSE_RUNTIME_NON_SKIPPINGnever do this.renderWorkflowRestartableImplcomputes its dirty bits withcomposer.changed(props), which always returns true on first composition. That reachesWorkflowSnapshotState.updateAndGetStateasdidPropsChange = true, even thoughComposeRenderContextwas just created with those same props.Found while writing tests for CLF-654 (#1591).
RenderWorkflowInTest. It fails only onCOMPOSE_RUNTIME_SKIPPING.composer.inserting), report props as unchanged andonOutputas changed.WorkflowSnapshotStatestarts withonOutput = null, and the spurious props-changed write was the thing that stored the real handler. Simply falling back toequalsbroke output delivery for the root workflow and added an extra propsequalscall.🤖 Generated with Claude Code