mutable_state_rebuilder.go ×3

Frontier kind: Joint frontier

unlabeled · c_e5578099c403

1 test · 4414 LOC · 194 files · introduces 1 test · 23 LOC · 2 files

Introduces — evidence that enters the hierarchy at this concept

Code
5 ranges23 lines · 2 files
Tests
1 test

Contains — complete concept membership

All code (extent)
685 ranges4414 lines · 194 files · Browse complete extent
All tests (intent)
1 testBrowse 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.

1 test introduced at this concept.

Introduced code

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

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

go.temporal.io/server/service/history/workflow/mutable_state_rebuilder.go 13 introduced LOC · 3 ranges

Open complete file

262 }
263
264 > case enumspb.EVENT_TYPE_WORKFLOW_TASK_TIMED_OUT: mutable_state_rebuilder.go
265 > if err := b.mutableState.ApplyWorkflowTaskTimedOutEvent(
266 > event.GetWorkflowTaskTimedOutEventAttributes().GetTimeoutType(),
267 > ); err != nil {
268 return nil, err
269 }
270
271 // this is for transient workflowTask
272 > workflowTask, err := b.mutableState.ApplyTransientWorkflowTaskScheduled() mutable_state_rebuilder.go
273 > if err != nil {
274 return nil, err
275 }
276
277 > if workflowTask != nil { mutable_state_rebuilder.go
278 > // since we do not use stickiness on the standby side
279 > // there shall be no workflowTask schedule to start timeout
280 > // NOTE: at the beginning of the loop, stickyness is cleared
281 > if err := taskGenerator.GenerateScheduleWorkflowTaskTasks(
282 > workflowTask.ScheduledEventID,
283 > ); err != nil {
284 return nil, err
285 }
go.temporal.io/server/service/history/interfaces/mutable_state_mock.go 10 introduced LOC · 2 ranges

Open complete file

1684
1685 // ApplyWorkflowTaskTimedOutEvent mocks base method.
1686 > func (m *MockMutableState) ApplyWorkflowTaskTimedOutEvent(arg0 enums.TimeoutType) error { mutable_state_mock.go
1687 > m.ctrl.T.Helper()
1688 > ret := m.ctrl.Call(m, "ApplyWorkflowTaskTimedOutEvent", arg0)
1689 > ret0, _ := ret[0].(error)
1690 > return ret0
1691 > }
1692
1693 // ApplyWorkflowTaskTimedOutEvent indicates an expected call of ApplyWorkflowTaskTimedOutEvent.
1694 > func (mr *MockMutableStateMockRecorder) ApplyWorkflowTaskTimedOutEvent(arg0 any) *gomock.Call { mutable_state_mock.go
1695 > mr.mock.ctrl.T.Helper()
1696 > return mr.mock.ctrl.RecordCallWithMethodType(mr.mock, "ApplyWorkflowTaskTimedOutEvent", reflect.TypeOf((*MockMutableState)(nil).ApplyWorkflowTaskTimedOutEvent), arg0)
1697 > }
1698
1699 // AttachRequestID mocks base method.