Vihren Atlas

context.go ×2

Code frontier

unlabeled · c_bdf1c12874dd

143 tests · 4251 LOC · 175 files · introduces 0 tests · 13 LOC · 2 files

Introduces — evidence that enters the hierarchy at this concept

Code
3 ranges13 lines · 2 files
Tests
0 tests

Contains — complete concept membership

All code (extent)
696 ranges4251 lines · 175 files · Browse complete extent
All tests (intent)
143 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: 13 introduced LOC across 3 ranges. Expand a file to inspect source; the > gutter marks introduced lines.

go.temporal.io/server/service/history/workflow/mutable_state_impl.go 10 introduced LOC · 1 range

Open complete file

1312 }
1313
1314 > func (ms *MutableStateImpl) IsCurrentWorkflowGuaranteed() bool { mutable_state_impl.go
1315 > // stateInDB is used like a bloom filter:
1316 > //
1317 > // 1. stateInDB being created / running meaning that this workflow must be the current
1318 > // workflow (assuming there is no rebuild of mutable state).
1319 > // 2. stateInDB being completed does not guarantee this workflow being the current workflow
1320 > // 3. stateInDB being zombie guarantees this workflow not being the current workflow
1321 > // 4. stateInDB cannot be void, void is only possible when mutable state is just initialized
1322 >
1323 > switch ms.stateInDB {
1324 case enumsspb.WORKFLOW_EXECUTION_STATE_VOID:
1325 return false
go.temporal.io/server/service/history/workflow/context.go 3 introduced LOC · 2 ranges

Open complete file

1079 }
1080
1081 > func (c *ContextImpl) updateWorkflowMode() (persistence.UpdateWorkflowMode, error) { context.go
1082 > if !c.config.EnableUpdateWorkflowModeIgnoreCurrent() {
1083 return persistence.UpdateWorkflowModeUpdateCurrent, nil
1084 }
1085
1086 > if c.MutableState.IsCurrentWorkflowGuaranteed() { context.go
1087 return persistence.UpdateWorkflowModeUpdateCurrent, nil
1088 }

Direct hierarchy

Parents

Children