workflow_resetter.go ×3

Frontier kind: Code frontier

unlabeled · c_3286cc64f7fe

20 tests · 2690 LOC · 137 files · introduces 0 tests · 13 LOC · 1 file

Introduces — evidence that enters the hierarchy at this concept

Code
3 ranges13 lines · 1 files
Tests
0 tests

Contains — complete concept membership

All code (extent)
396 ranges2690 lines · 137 files · Browse complete extent
All tests (intent)
20 testsBrowse complete intent

Neighbourhood graph

The orange circle is the focus. Violet and green circles are every ancestor and descendant, broader and narrower, at any distance; blue squares and pink diamonds are the introduced files and exact introduced tests of every visible concept, not only the focus's. Arrows point from broader to narrower concepts and bridge only concepts omitted from this view. Undirected links show source or test introduction. Concept and file size follows LOC; exact test nodes use test-count units.

Introduced files, introduced tests, and structurally relevant concept specialization

In the embedded map, ordinary wheel input scrolls the page; use the visible controls to zoom and drag to pan. Open the full-screen map for canvas navigation: wheel pans, Ctrl/Command plus wheel zooms, and arrow keys pan when this region is focused. On touch screens, open the full-screen map to pan or pinch. If JavaScript or WebGL is unavailable, use the native relationship evidence on this page.

Graph controls are ready.

Interactive rendering requires JavaScript and WebGL. Use the native relationship evidence on this page while the interactive map is unavailable.

Native relationship evidence

Every exact file and test below is linked only from the concept that introduces it.

Introduced tests

Every collected test enters the hierarchy at exactly one concept.

No tests are introduced at this concept. Its intent tests are introduced by other concepts.

Introduced code

Every collected source range enters the hierarchy at exactly one concept.

1 file ranked by introduced lines: 13 introduced LOC across 3 ranges. Expand a file to inspect source; the > gutter marks introduced lines.

go.temporal.io/server/service/history/ndc/workflow_resetter.go 13 introduced LOC · 3 ranges

Open complete file

1098 return nil, err
1099 }
1100 > default: workflow_resetter.go
1101 > // Nexus operations (and other state-machine-backed components) can be backed by either the HSM tree or the
1102 > // CHASM tree, and both coexist on the same mutable state. Reset must rebuild the op regardless of which
1103 > // framework owns it.
1104 > // TODO(follow-up): the completion-token resolution path (HSM StateMachineRef vs CHASM
1105 > // ComponentRef) also needs the same fallback; see the completion handler in nexusoperation.
1106 > outcome, err := cherryPickHSMEvent(mutableState, stateMachineRegistry, event, resetReapplyExcludeTypes)
1107 > if err != nil {
1108 return reappliedEvents, err
1109 }
1110 > if outcome == cherryPickFallback { workflow_resetter.go
1111 > // HSM doesn't own this op (unknown type, or component not in the HSM tree): try the CHASM tree.
1112 > outcome, err = cherryPickChasmEvent(ctx, mutableState, chasmWorkflowRegistry, event, resetReapplyExcludeTypes)
1113 > if err != nil {
1114 return reappliedEvents, err
1115 }
1116 }
1117 > if outcome != cherryPickApplied { workflow_resetter.go
1118 // Either skipped (recognized but not cherry-pickable) or unhandled by both frameworks.
1119 // Only reapply hardcoded events above or ones cherry-picked in HSM or CHASM.