Vihren Atlas

interceptors.go ×1

Code frontier

unlabeled · c_a97e680f387a

11 tests · 1898 LOC · 83 files · introduces 0 tests · 11 LOC · 2 files

Introduces — evidence that enters the hierarchy at this concept

Code
2 ranges11 lines · 2 files
Tests
0 tests

Contains — complete concept membership

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

go.temporal.io/server/chasm/interceptors.go 8 introduced LOC · 1 range

Open complete file

24 info *grpc.UnaryServerInfo,
25 handler grpc.UnaryHandler,
26 > ) (resp any, retError error) { interceptors.go
27 > // Capture panics for any handler method, not just CHASM-specific ones. This could have gone into a separate
28 > // interceptor, but having it here avoids the overhead of adding another layer to the interceptor chain.
29 > defer metrics.CapturePanic(i.logger, i.metricsHandler, &retError)
30 >
31 > ctx = NewEngineContext(ctx, i.engine)
32 > return handler(ctx, req)
33 > }
34
35 func ChasmEngineInterceptorProvider(
go.temporal.io/server/common/metrics/panic.go 3 introduced LOC · 1 range

Open complete file

13 // We have to use pointer is because in golang: "recover return nil if was not called directly by a deferred function."
14 // And we have to set the returned error otherwise our handler will return nil as error which is incorrect
15 > func CapturePanic(logger log.Logger, metricHandler Handler, retError *error) { panic.go
16 > //revive:disable-next-line:defer
17 > if pObj := recover(); pObj != nil {
18 err, ok := pObj.(error)
19 if !ok {

Direct hierarchy

Parents

Children