Vihren Atlas

chasm_task.go ×2

Code frontier

unlabeled · c_b2e27c1f97cd

4 tests · 4988 LOC · 212 files · introduces 0 tests · 17 LOC · 5 files

Introduces — evidence that enters the hierarchy at this concept

Code
6 ranges17 lines · 5 files
Tests
0 tests

Contains — complete concept membership

All code (extent)
795 ranges4988 lines · 212 files · Browse complete extent
All tests (intent)
4 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.

5 files ranked by introduced lines: 17 introduced LOC across 6 ranges. Expand a file to inspect source; the > gutter marks introduced lines.

go.temporal.io/server/service/history/tasks/chasm_task.go 6 introduced LOC · 2 ranges

Open complete file

23 var _ HasArchetypeID = &ChasmTaskPure{}
24
25 > func (t *ChasmTaskPure) GetTaskID() int64 { chasm_task.go
26 > return t.TaskID
27 > }
28
29 func (t *ChasmTaskPure) SetTaskID(id int64) {
31 }
32
33 > func (t *ChasmTaskPure) GetVisibilityTime() time.Time { chasm_task.go
34 > return t.VisibilityTimestamp
35 > }
36
37 func (t *ChasmTaskPure) SetVisibilityTime(timestamp time.Time) {
go.temporal.io/server/service/history/timer_queue_task_executor_base.go 5 introduced LOC · 1 range

Open complete file

263 task *tasks.ChasmTaskPure,
264 callback func(node chasm.NodePureTask, taskAttributes chasm.TaskAttributes, task any) (bool, error),
265 > ) error { timer_queue_task_executor_base.go
266 > // Because CHASM timers can target closed workflows, we need to specifically
267 > // exclude zombie workflows, instead of merely checking that the workflow is
268 > // running.
269 > if ms.GetExecutionState().State == enumsspb.WORKFLOW_EXECUTION_STATE_ZOMBIE {
270 return consts.ErrWorkflowZombie
271 }
go.temporal.io/server/api/enums/v1/task.pb.go 2 introduced LOC · 1 range

Open complete file

287 case TASK_TYPE_REPLICATION_SYNC_VERSIONED_TRANSITION:
288 return "ReplicationSyncVersionedTransition"
289 > case TASK_TYPE_CHASM_PURE: task.pb.go
290 > return "ChasmPure"
291 case TASK_TYPE_CHASM:
292 return "Chasm"
go.temporal.io/server/service/history/queues/metrics.go 2 introduced LOC · 1 range

Open complete file

112 case *tasks.ChasmTask:
113 return prefix + "." + getCHASMTaskTypeTagValue(t, chasmRegistry)
114 > case *tasks.ChasmTaskPure: metrics.go
115 > return metrics.TaskTypeTimerActiveTaskChasmPureTask
116 case *tasks.TimeSkippingTimerTask:
117 return metrics.TaskTypeTimerActiveTaskTimeSkippingTimer
go.temporal.io/server/service/history/tasks/utils.go 2 introduced LOC · 1 range

Open complete file

117 // and it doesn't depend on eventID, so it uses the dummy chasm task eventID here.
118 return getChasmTaskEventID()
119 > case *ChasmTaskPure: utils.go
120 > return getChasmTaskEventID()
121 case *ChasmTask:
122 return getChasmTaskEventID()

Direct hierarchy

Parents

Children