Vihren Atlas

api.go ×1

Code frontier

unlabeled · c_0b6a0a46d1c5

11 tests · 8299 LOC · 213 files · introduces 0 tests · 16 LOC · 2 files

Introduces — evidence that enters the hierarchy at this concept

Code
2 ranges16 lines · 2 files
Tests
0 tests

Contains — complete concept membership

All code (extent)
1814 ranges8299 lines · 213 files · Browse complete extent
All tests (intent)
11 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: 16 introduced LOC across 2 ranges. Expand a file to inspect source; the > gutter marks introduced lines.

go.temporal.io/server/service/history/api/respondworkflowtaskcompleted/api.go 12 introduced LOC · 1 range

Open complete file

351 ms.ClearStickyTaskQueue()
352 } else {
353 > metrics.CompleteWorkflowTaskWithStickyEnabledCounter.With(handler.metricsHandler).Record( api.go
354 > 1,
355 > metrics.OperationTag(metrics.HistoryRespondWorkflowTaskCompletedScope))
356 > if (assignedBuildId == "" || assignedBuildId == wftCompletedBuildId) &&
357 > (ms.GetDeploymentTransition() == nil || ms.GetDeploymentTransition().GetDeployment().Equal(deployment)) {
358 > // TODO: clean up. this is not applicable to V3
359 > // For versioned workflows, only set sticky queue if the WFT is completed by the WF's current build ID.
360 > // It is possible that the WF has been redirected to another build ID since this WFT started, in that case
361 > // we should not set sticky queue of the old build ID and keep the normal queue to let Matching send the
362 > // next WFT to the right build ID.
363 > ms.SetStickyTaskQueue(request.StickyAttributes.WorkerTaskQueue.GetName(), request.StickyAttributes.GetScheduleToStartTimeout())
364 > }
365 }
366
go.temporal.io/server/service/history/workflow/mutable_state_impl.go 4 introduced LOC · 1 range

Open complete file

1443 }
1444
1445 > func (ms *MutableStateImpl) SetStickyTaskQueue(name string, scheduleToStartTimeout *durationpb.Duration) { mutable_state_impl.go
1446 > ms.executionInfo.StickyTaskQueue = name
1447 > ms.executionInfo.StickyScheduleToStartTimeout = scheduleToStartTimeout
1448 > }
1449
1450 func (ms *MutableStateImpl) ClearStickyTaskQueue() {

Direct hierarchy

Parents

Children