Vihren Atlas

mutable_state_impl.go ×5

Code frontier

unlabeled · c_d6fff94ec731

62 tests · 4406 LOC · 175 files · introduces 0 tests · 17 LOC · 2 files

Introduces — evidence that enters the hierarchy at this concept

Code
7 ranges17 lines · 2 files
Tests
0 tests

Contains — complete concept membership

All code (extent)
752 ranges4406 lines · 175 files · Browse complete extent
All tests (intent)
62 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.

2 files ranked by introduced lines: 17 introduced LOC across 7 ranges. Expand a file to inspect source; the > gutter marks introduced lines.

go.temporal.io/server/service/history/workflow/mutable_state_impl.go 9 introduced LOC · 5 ranges

Open complete file

7189 // processCloseCallbacks triggers "WorkflowClosed" callbacks, applying the state machine transition that schedules
7190 // callback tasks.
7191 > func (ms *MutableStateImpl) processCloseCallbacks() error { mutable_state_impl.go
7192 > resetRunID := ms.GetExecutionInfo().GetResetRunId()
7193 > if ms.GetExecutionInfo().GetWorkflowWasReset() && resetRunID != "" && resetRunID != ms.executionState.RunId {
7194 return nil
7195 }
7199 // were enabled can still be triggered even if the EnableCHASMCallbacks dynamic config is later
7200 // turned off. Once created in CHASM, callbacks should always be processed as long as CHASM is enabled.
7201 > if ms.ChasmEnabled() { mutable_state_impl.go
7202 if err := ms.processCloseCallbacksChasm(); err != nil {
7203 return err
7206
7207 // Always process HSM callbacks as well (a workflow can have both)
7208 > return ms.processCloseCallbacksHsm() mutable_state_impl.go
7209 }
7210
7211 // processCloseCallbacksHsm triggers "WorkflowClosed" callbacks using the HSM implementation.
7212 > func (ms *MutableStateImpl) processCloseCallbacksHsm() error { mutable_state_impl.go
7213 > coll := callbacks.MachineCollection(ms.HSM())
7214 > for _, node := range coll.List() {
7215 cb, err := coll.Data(node.Key.ID)
7216 if err != nil {
go.temporal.io/server/api/persistence/v1/executions.pb.go 8 introduced LOC · 2 ranges

Open complete file

1026 }
1027
1028 > func (x *WorkflowExecutionInfo) GetWorkflowWasReset() bool { executions.pb.go
1029 > if x != nil {
1030 > return x.WorkflowWasReset
1031 > }
1032 return false
1033 }
1034
1035 > func (x *WorkflowExecutionInfo) GetResetRunId() string { executions.pb.go
1036 > if x != nil {
1037 > return x.ResetRunId
1038 > }
1039 return ""
1040 }

Direct hierarchy

Parents

Children