Vihren Atlas

task_generator.go ×4

Code frontier

unlabeled · c_345119c2fdd7

281 tests · 4228 LOC · 170 files · introduces 0 tests · 20 LOC · 1 file

Introduces — evidence that enters the hierarchy at this concept

Code
4 ranges20 lines · 1 files
Tests
0 tests

Contains — complete concept membership

All code (extent)
689 ranges4228 lines · 170 files · Browse complete extent
All tests (intent)
281 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: 20 introduced LOC across 4 ranges. Expand a file to inspect source; the > gutter marks introduced lines.

go.temporal.io/server/service/history/workflow/task_generator.go 20 introduced LOC · 4 ranges

Open complete file

422 func (r *TaskGeneratorImpl) GenerateScheduleWorkflowTaskTasks(
423 workflowTaskScheduledEventID int64,
424 > ) error { task_generator.go
425 > workflowTask := r.mutableState.GetWorkflowTaskByID(workflowTaskScheduledEventID)
426 > if workflowTask == nil {
427 return serviceerror.NewInternalf("it could be a bug, cannot get pending workflow task: %v", workflowTaskScheduledEventID)
428 }
429 > if workflowTask.Type == enumsspb.WORKFLOW_TASK_TYPE_SPECULATIVE { task_generator.go
430 return serviceerror.NewInternalf("it could be a bug, GenerateScheduleSpeculativeWorkflowTaskTasks must be called for speculative workflow task: %v", workflowTaskScheduledEventID)
431 }
432
433 > if r.mutableState.IsStickyTaskQueueSet() { task_generator.go
434 scheduleToStartTimeout := timestamp.DurationValue(r.mutableState.GetExecutionInfo().StickyScheduleToStartTimeout)
435 wttt := &tasks.WorkflowTaskTimeoutTask{
447 }
448
449 > r.mutableState.AddTasks(&tasks.WorkflowTask{ task_generator.go
450 > // TaskID, VisibilityTimestamp is set by shard
451 > WorkflowKey: r.mutableState.GetWorkflowKey(),
452 > // Store current task queue to the transfer task.
453 > // If current task queue becomes sticky in between when this transfer task is created and processed,
454 > // it can't be used at process time, because timeout timer was not created for it,
455 > // because it used to be non-sticky when this transfer task was created here.
456 > // In short, task queue that was "current" when transfer task was created must be used when task is processed.
457 > TaskQueue: workflowTask.TaskQueue.GetName(),
458 > ScheduledEventID: workflowTask.ScheduledEventID,
459 > Version: workflowTask.Version,
460 > Stamp: workflowTask.Stamp,
461 > })
462 >
463 > return nil
464 }
465

Direct hierarchy

Parents

Children