Vihren Atlas

timer_queue_standby_task_executor.go ×2

Code frontier

unlabeled · c_85e907dab246

2 tests · 5374 LOC · 223 files · introduces 0 tests · 20 LOC · 2 files

Introduces — evidence that enters the hierarchy at this concept

Code
4 ranges20 lines · 2 files
Tests
0 tests

Contains — complete concept membership

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

go.temporal.io/server/service/history/timer_queue_task_executor_base.go 12 introduced LOC · 2 ranges

Open complete file

252
253 if err := execute(node, smt); err != nil {
254 > return fmt.Errorf("failed to execute task: %w", err) timer_queue_task_executor_base.go
255 > }
256 return nil
257 }
319 // This includes errors such as ErrStaleReference and ErrWorkflowCompleted.
320 if !errors.As(err, new(*serviceerror.NotFound)) {
321 > metrics.StateMachineTimerProcessingFailuresCounter.With(t.metricsHandler).Record( timer_queue_task_executor_base.go
322 > 1,
323 > metrics.OperationTag(queues.GetTimerStateMachineTaskTypeTagValue(timer.GetType(), t.isActive)),
324 > metrics.ServiceErrorTypeTag(err),
325 > )
326 > // Return on first error as we don't want to duplicate the Executable's error handling logic.
327 > // This implies that a single bad task in the mutable state timer sequence will cause all other
328 > // tasks to be stuck. We'll accept this limitation for now.
329 > return 0, err
330 > }
331 metrics.StateMachineTimerSkipsCounter.With(t.metricsHandler).Record(
332 1,
go.temporal.io/server/service/history/timer_queue_standby_task_executor.go 8 introduced LOC · 2 ranges

Open complete file

668 timerTask,
669 func(node *hsm.Node, task hsm.Task) error {
670 > // If this line of code is reached, the task's Validate() function returned no error, which indicates timer_queue_standby_task_executor.go
671 > // that it is still expected to run. Return ErrTaskRetry to wait the machine to transition on the active
672 > // cluster.
673 > return consts.ErrTaskRetry
674 > },
675 )
676 if err != nil {
677 if errors.Is(err, consts.ErrTaskRetry) {
678 > // This handles the ErrTaskRetry error returned by executeStateMachineTimers. timer_queue_standby_task_executor.go
679 > return &struct{}{}, nil
680 > }
681 return nil, err
682 }

Direct hierarchy

Parents

Children