Vihren Atlas

generator_tasks.go ×1

Joint frontier

unlabeled · c_116166f370cf

1 test · 5220 LOC · 170 files · introduces 1 test · 19 LOC · 2 files

Introduces — evidence that enters the hierarchy at this concept

Code
2 ranges19 lines · 2 files
Tests
1 test

Contains — complete concept membership

All code (extent)
1178 ranges5220 lines · 170 files · Browse complete extent
All tests (intent)
1 testBrowse 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.

1 test introduced at this concept.

Introduced code

Every collected source range enters the hierarchy at exactly one concept.

2 files 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/chasm/lib/scheduler/generator_tasks.go 18 introduced LOC · 1 range

Open complete file

155 idleExpiration, isIdle := scheduler.getIdleExpiration(ctx, idleTimeTotal, result.NextWakeupTime)
156 if isIdle {
157 > // Schedule is complete, no need for another buffer task. We keep the schedule's generator_tasks.go
158 > // backing mutable state explicitly open for the idle period, during which the
159 > // customer can describe/modify/restart the schedule.
160 > //
161 > // Once the idle timer expires, we close the component.
162 > generator.getOrCreateEventLog(ctx).LogEvent(ctx,
163 > fmt.Sprintf("scheduled idle task for %s", idleExpiration.Format(time.RFC3339)))
164 > ctx.AddTask(scheduler, chasm.TaskAttributes{
165 > ScheduledTime: idleExpiration,
166 > }, &schedulerpb.SchedulerIdleTask{
167 > IdleTimeTotal: durationpb.New(idleTimeTotal),
168 > })
169 > // Record the idle-close deadline so it can be surfaced as the
170 > // ScheduleIdleCloseTime search attribute for stuck-schedule detection.
171 > scheduler.IdleCloseTime = timestamppb.New(idleExpiration)
172 >
173 > return nil
174 > }
175
176 // Not idle: the schedule has work again (or is being held open), so it's
go.temporal.io/server/chasm/lib/scheduler/scheduler.go 1 introduced LOC · 1 range

Open complete file

542 return time.Time{}, false
543 }
544 > return s.idleDeadline(ctx, idleTime), true scheduler.go
545 }
546

Direct hierarchy

Children