You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
csharp: a registered gRPC interceptor is not an entry point, so impact calls a change to it local #1489
A C# gRPC interceptor, a subclass of Grpc.Core.Interceptors.Interceptor registered with AddGrpc(o => o.Interceptors.Add<T>()), is not an entry point, so impact on its handler says nothing depends on it and the change is local. A hosted service in the same file is a lifecycle entry point. Measured on 0.1.3 at 0df257c; CLI impact and the MCP axiomcode_impact tool agree.
axiomcode impact LoggingInterceptor.UnaryServerHandler prints no entry point, three [alongside] rows and next: nothing resolved depends on it, so the change is local -- read src/Program.cs:9 and edit there. The control impact Heartbeat.ExecuteAsync prints Heartbeat.ExecuteAsync is a lifecycle entry point.
Root cause
graph/csharp/engine/framework-behavior/entry-points.dl:14-34 has rules for main, tests, served routes/rpcs/consumers and hosted services (cs_hosted_base, knobs.dl:204-205) only. No knob or rule names Interceptor or its overridable handlers.
Expected
An override of an Interceptor handler on a registered interceptor is a framework-invoked entry point, so impact does not call a change to it local.
Activity
swapnilpaliwal-sd commentedon Sep 28, 2026
Fixed by #1620.