Vihren Atlas

workflow_resetter.go ×2

Code frontier

unlabeled · c_feae1a39afec

51 tests · 2659 LOC · 137 files · introduces 0 tests · 9 LOC · 1 file

Introduces — evidence that enters the hierarchy at this concept

Code
2 ranges9 lines · 1 files
Tests
0 tests

Contains — complete concept membership

All code (extent)
388 ranges2659 lines · 137 files · Browse complete extent
All tests (intent)
51 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: 9 introduced LOC across 2 ranges. Expand a file to inspect source; the > gutter marks introduced lines.

go.temporal.io/server/service/history/ndc/workflow_resetter.go 9 introduced LOC · 2 ranges

Open complete file

934 runIdForDeduplication string,
935 isReset bool,
936 > ) ([]*historypb.HistoryEvent, error) { workflow_resetter.go
937 > // TODO (dan): This implementation is the result of unifying two previous implementations, one of which did
938 > // deduplication. Can we always/never do this deduplication, or must it be decided by the caller?
939 > isDuplicate := func(event *historypb.HistoryEvent) bool {
940 if runIdForDeduplication == "" {
941 return false
944 return mutableState.IsResourceDuplicated(resource)
945 }
946 > _, excludeSignal := resetReapplyExcludeTypes[enumspb.RESET_REAPPLY_EXCLUDE_TYPE_SIGNAL] workflow_resetter.go
947 > _, excludeUpdate := resetReapplyExcludeTypes[enumspb.RESET_REAPPLY_EXCLUDE_TYPE_UPDATE]
948 > var reappliedEvents []*historypb.HistoryEvent
949 > for _, event := range events {
950 > switch event.GetEventType() {
951 case enumspb.EVENT_TYPE_WORKFLOW_EXECUTION_SIGNALED:
952 if excludeSignal || isDuplicate(event) {

Direct hierarchy

Parents

Children