physical_task_queue_manager.go ×2

Frontier kind: Code frontier

unlabeled · c_f69939c37fcc

236 tests · 3624 LOC · 170 files · introduces 0 tests · 19 LOC · 1 file

Introduces — evidence that enters the hierarchy at this concept

Code
2 ranges19 lines · 1 files
Tests
0 tests

Contains — complete concept membership

All code (extent)
611 ranges3624 lines · 170 files · Browse complete extent
All tests (intent)
236 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: 19 introduced LOC across 2 ranges. Expand a file to inspect source; the > gutter marks introduced lines.

go.temporal.io/server/service/matching/physical_task_queue_manager.go 19 introduced LOC · 2 ranges

Open complete file

969 priorityKey priorityKey,
970 n int,
972 > // priorityKey could be zero here if we're tracking dispatched tasks (i.e. called from PollTask)
973 > // and the poll was forwarded so we have a "started" task. We don't return the priority with the
974 > // started task info so it's not available here. Use the default priority to avoid confusion
975 > // even though it may not be accurate.
976 > // TODO: either return priority with the started task, or do this tracking on the node where the
977 > // match happened, so we have the right value here.
978 > if priorityKey == 0 {
979 priorityKey = c.config.DefaultPriorityKey
980 }
981
982 > c.taskTrackerLock.Lock() physical_task_queue_manager.go
983 > defer c.taskTrackerLock.Unlock()
984 >
985 > tracker, ok := intervals[priorityKey]
986 > if !ok {
987 > // Initialize all task trackers together; or the timeframes won't line up.
988 > c.tasksAdded[priorityKey] = c.partitionMgr.engine.newTaskTracker()
989 > c.tasksDispatched[priorityKey] = c.partitionMgr.engine.newTaskTracker()
990 > tracker = intervals[priorityKey]
991 > }
992 > tracker.inc(n)
993 }
994