Vihren Atlas

matching_engine.go ×1

Code frontier

unlabeled · c_271bc0e88d4e

3 tests · 6403 LOC · 199 files · introduces 0 tests · 12 LOC · 1 file

Introduces — evidence that enters the hierarchy at this concept

Code
1 range12 lines · 1 files
Tests
0 tests

Contains — complete concept membership

All code (extent)
1397 ranges6403 lines · 199 files · Browse complete extent
All tests (intent)
3 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: 12 introduced LOC across 1 ranges. Expand a file to inspect source; the > gutter marks introduced lines.

go.temporal.io/server/service/matching/matching_engine.go 12 introduced LOC · 1 range

Open complete file

807 e.logger.Debug("Duplicated workflow task", tag.WorkflowTaskQueueName(taskQueueName), tag.TaskID(task.event.GetTaskId()))
808 task.finish(taskFinishResult{dropReason: dropReasonInvalid})
809 > case *serviceerrors.ObsoleteDispatchBuildId: matching_engine.go
810 > // history should've scheduled another task on the right build ID. dropping this one.
811 > e.logger.Info("dropping workflow task due to invalid build ID",
812 > tag.WorkflowTaskQueueName(taskQueueName),
813 > tag.WorkflowNamespaceID(task.event.Data.GetNamespaceId()),
814 > tag.WorkflowID(task.event.Data.GetWorkflowId()),
815 > tag.WorkflowRunID(task.event.Data.GetRunId()),
816 > tag.TaskID(task.event.GetTaskId()),
817 > tag.TaskVisibilityTimestamp(timestamp.TimeValue(task.event.Data.GetCreateTime())),
818 > tag.BuildId(requestClone.WorkerVersionCapabilities.GetBuildId()),
819 > )
820 > task.finish(taskFinishResult{dropReason: dropReasonInvalid})
821 case *serviceerrors.ObsoleteMatchingTask:
822 // History should've scheduled another task on the right task queue and deployment.

Direct hierarchy

Parents

Children