Vihren Atlas

activity.go ×1

Code frontier

unlabeled · c_55d77c5596f7

4 tests · 2395 LOC · 120 files · introduces 0 tests · 29 LOC · 2 files

Introduces — evidence that enters the hierarchy at this concept

Code
2 ranges29 lines · 2 files
Tests
0 tests

Contains — complete concept membership

All code (extent)
358 ranges2395 lines · 120 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.

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

go.temporal.io/server/chasm/lib/activity/statemachine.go 24 introduced LOC · 1 range

Open complete file

270 },
271 activitypb.ACTIVITY_EXECUTION_STATUS_TERMINATED,
272 > func(a *Activity, ctx chasm.MutableContext, event terminateEvent) error { statemachine.go
273 > return a.StoreOrSelf(ctx).RecordCompleted(ctx, func(ctx chasm.MutableContext) error {
274 > a.TerminateState = &activitypb.ActivityTerminateState{
275 > RequestId: event.request.RequestID,
276 > }
277 > outcome := a.Outcome.Get(ctx)
278 > failure := &failurepb.Failure{
279 > Message: event.request.Reason,
280 > FailureInfo: &failurepb.Failure_TerminatedFailureInfo{
281 > TerminatedFailureInfo: &failurepb.TerminatedFailureInfo{
282 > Identity: event.request.Identity,
283 > },
284 > },
285 > }
286 > outcome.Variant = &activitypb.ActivityOutcome_Failed_{
287 > Failed: &activitypb.ActivityOutcome_Failed{
288 > Failure: failure,
289 > },
290 > }
291 >
292 > a.emitOnTerminatedMetrics(event.metricsHandler)
293 >
294 > return nil
295 > })
296 },
297 )
go.temporal.io/server/chasm/lib/activity/activity.go 5 introduced LOC · 1 range

Open complete file

2001 func (a *Activity) emitOnTerminatedMetrics(
2002 handler metrics.Handler,
2003 > ) { activity.go
2004 > // Terminated activities do not count as properly finished activities so we do not
2005 > // record any of the latency metrics.
2006 > metrics.ActivityTerminate.With(handler).Record(1)
2007 > }
2008
2009 func (a *Activity) emitOnCanceledMetrics(

Direct hierarchy

Parents

Children