Vihren Atlas

task_queue_partition_manager.go ×4

Code frontier

unlabeled · c_23d1a5a9525f

30 tests · 4443 LOC · 175 files · introduces 0 tests · 13 LOC · 1 file

Introduces — evidence that enters the hierarchy at this concept

Code
4 ranges13 lines · 1 files
Tests
0 tests

Contains — complete concept membership

All code (extent)
835 ranges4443 lines · 175 files · Browse complete extent
All tests (intent)
30 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: 13 introduced LOC across 4 ranges. Expand a file to inspect source; the > gutter marks introduced lines.

go.temporal.io/server/service/matching/task_queue_partition_manager.go 13 introduced LOC · 4 ranges

Open complete file

620 syncMatched = outcome == syncMatchSuccess
621 if syncMatched && !pm.shouldBacklogSyncMatchTaskOnError(err) {
622 > // Only fire hooks for non-forwarded tasks. Forwarded tasks already had hooks fired task_queue_partition_manager.go
623 > // on the child partition that originally received the task.
624 > if !forwarded {
625 // We should not use targetVersion because targetVersion is always routing-config-deriven.
626 // For pinned workflows, targetVersion is not necessarily the same as the pinned version.
628 }
629
630 > syncMatchResult := metrics.TaskAddResultSyncMatch task_queue_partition_manager.go
631 > if err != nil {
632 syncMatchResult = taskAddErrResult(err)
633 }
634 > syncMatchQueue.RecordTaskAdd(syncMatchResult, forwarded, behavior) task_queue_partition_manager.go
635 >
636 > // Build ID is not returned for sync match. The returned build ID is used by History to update
637 > // mutable state (and visibility) when the first workflow task is spooled.
638 > // For sync-match case, History has already received the build ID in the Record*TaskStarted call.
639 > // By omitting the build ID from this response we help History immediately know that no MS update is needed.
640 > return "", syncMatched, err
641 } else if errors.Is(err, errReprocessTask) {
642 // We get this if userdata changed while the task was blocked in TrySyncMatch

Direct hierarchy

Parents

Children