completion.go ×2

Frontier kind: Code frontier

unlabeled · c_48777a8af3ed

3 tests · 3088 LOC · 139 files · introduces 0 tests · 19 LOC · 2 files

Introduces — evidence that enters the hierarchy at this concept

Code
3 ranges19 lines · 2 files
Tests
0 tests

Contains — complete concept membership

All code (extent)
544 ranges3088 lines · 139 files · Browse complete extent
All tests (intent)
3 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: 19 introduced LOC across 3 ranges. Expand a file to inspect source; the > gutter marks introduced lines.

go.temporal.io/server/components/nexusoperations/completion.go 16 introduced LOC · 2 ranges

Open complete file

24 result *commonpb.Payload,
25 links []*commonpb.Link,
26 > ) error { completion.go
27 > eventID, err := hsm.EventIDFromToken(operation.ScheduledEventToken)
28 > if err != nil {
29 return err
30 }
31 > event := node.AddHistoryEvent(enumspb.EVENT_TYPE_NEXUS_OPERATION_COMPLETED, func(e *historypb.HistoryEvent) { completion.go
32 > // We must assign to this property, linter doesn't like this.
33 > // nolint:revive
34 > e.Attributes = &historypb.HistoryEvent_NexusOperationCompletedEventAttributes{
35 > NexusOperationCompletedEventAttributes: &historypb.NexusOperationCompletedEventAttributes{
36 > ScheduledEventId: eventID,
37 > Result: result,
38 > RequestId: operation.RequestId,
39 > },
40 > }
41 > e.Links = links
42 > })
43 > return CompletedEventDefinition{}.Apply(node.Parent, event)
44 }
45
go.temporal.io/server/components/nexusoperations/metrics.go 3 introduced LOC · 1 range

Open complete file

42 // emitOperationSucceeded emits the success counter and latency metrics for an operation that
43 // completed successfully.
44 > func emitOperationSucceeded(base metrics.Handler, tagConfig chasmnexus.NexusMetricTagConfig, op Operation, namespaceName, workflowType string, closeTime time.Time) { metrics.go
45 > emitOperationOutcome(base, tagConfig, op, namespaceName, workflowType, nexusoperationpb.OPERATION_STATUS_SUCCEEDED, closeTime, chasmnexus.NexusOperationSuccessCount.With)
46 > }
47
48 // emitOperationFailed emits the failure counter and latency metrics for an operation that