Failure Signatures - what the crash means and where the cause actually lives
Every runtime failure has a signature, and the signature names where to look - which is almost never the line in the top frame. This is the single-chat form of the diagnoser seat's failure catalogue: match the evidence to a signature, then isolate at the place the signature points, not the place it threw. It pairs with habits-root-cause - the disciplined hypothesis-and-test loop; this one tells you which hypothesis the signature warrants. Read the evidence first and quote the exact frame, then match.
When to use
Use when something breaks at runtime and you have the evidence - a stack trace, an exception, a hang or a broken screen, on your own machine or in a production event that carries the trace - and want to know where the real cause lives.
Not for a CI or build/test-gate failure (the resolvers and the CI diagnoser own those). When the evidence spans more than one source, the gatherer fan-out below handles it; a run with a gate between every step is the user's gated investigation command.
The signatures - and where each isolates
- Null-reference / undefined access (
NullReferenceException, Cannot read properties of undefined/null). The frame names the dereference, but the cause is usually one hop up: a dependency never assigned, or a value read across an async gap before its await resolved (an @Input touched in the constructor before ngOnInit, a field read before the task that sets it finished). Isolate by walking the assignment of the null symbol, not the line that dereferenced it.
- DI / composition-root failure (
Unable to resolve service for type, a startup InvalidOperationException, Angular NG0201). The injection site is innocent - the registration is missing, mis-scoped, or a captive dependency (a singleton capturing a scoped service). Isolate at the composition root (the container setup / module providers), never the consuming class.
- Async deadlock / sync-over-async (a hang, not a crash).
.Result / .Wait() / .GetAwaiter().GetResult() blocking a captured synchronization context (the classic WPF / WinForms UI-thread and ASP.NET-request deadlock), or a TaskCompletionSource never completed. Isolate to the sync-over-async boundary, not the innermost await.
- Race / shared mutable state (reproduces under load or a specific ordering, passes in isolation). A
static or singleton mutated concurrently, an un-awaited fire-and-forget, subscriptions firing out of order. Isolate by naming the shared cell and its competing writers, not by re-running until green.
- Disposed / lifecycle (
ObjectDisposedException, Cannot access a disposed context). A DbContext or HttpClient captured past its scope, a subscription or timer firing after teardown, a handler outliving its view. Isolate to the lifetime boundary that ended early, not the use site.
- Database contention / exhaustion (a query that deadlocks, times out, or violates a constraint under concurrency but is fine in isolation). A deadlock victim (SQL Server error 1205, Postgres 'deadlock detected') from two transactions taking locks in opposite order; connection-pool exhaustion (a timeout acquiring a pooled connection - usually a leaked or un-disposed connection or
DbContext, or sync-over-async starving the pool); or a unique / foreign-key violation surfacing a lost race. Isolate to the competing transactions and their lock order, or the connection that was never returned - not the statement that happened to lose.
- Config / environment drift (a value read as null or wrong, no crash at the read). A missing user secret / env var /
appsettings key, a connection string pointing at the wrong database, a WPF binding silently no-op'ing (the System.Windows.Data error in the Output window). Isolate by proving the value the code actually received, not the value it expected.
- Boundary / off-by-one (
IndexOutOfRangeException, ArgumentOutOfRangeException, an empty-sequence .First() / .Single()). A fencepost in a slice or loop, an empty collection assumed non-empty. Isolate to the boundary input that triggers it, and keep it as the regression case the fix must cover.
- HTTP error with a clean response (a returned status, no stack trace). Triage by the status class - it names the failing layer before you open a trace: 401 authentication, 403 authorization / policy, 400 / 422 validation, 404 routing / binding, 405 verb, an antiforgery or CORS-preflight rejection. Isolate at the layer the status names, not the handler body.
Execution modes
This catalogue is single-sourced: the issue-diagnoser-runtime seat preloads this same file, so
the inline and seated forms never drift. Loaded INSIDE the seat, this section is already satisfied
- the seat is the dispatched form, and the rest of this section is not read there. Loaded in the
MAIN session, run the triage HERE and Read
references/gatherer-fan-out.md before deciding on
evidence-gatherers - the inherit-or-ask rule, the four dispatch triggers, the stay-inline shapes
and a worked fan-out are that file. Either way, dispatch is explicit-only house-wide, so the seats
never start on your own say-so. Do NOT dispatch the diagnoser seat from this skill - the
signatures are already in context, so the seat would only duplicate them; the seat exists for the
orchestrated issue flow and direct @agent- calls, where it runs this same file in an isolated
context with the same gatherer fan-out.
How to use it
Match the evidence to one signature, form the fewest hypotheses it warrants, and confirm each against located code before you touch anything - root cause before symptom, never a plausible guess. State the match in four lines - the quoted evidence, the signature, the isolation point and the hypothesis it warrants - plus the proof line once the check has run, then run the loop:
Evidence: 'ObjectDisposedException: Cannot access a disposed context instance' in OrderSyncJob.ExecuteAsync
Signature: disposed / lifecycle - a DbContext captured past its scope.
Isolate: the lifetime boundary - the scoped DbContext resolved once and stored on the singleton job - not the query line that threw.
Hypothesis: the singleton job stores the scoped DbContext it resolved at startup
Proof: <the log or breakpoint at the boundary, quoted> | unproven - <what would decide it>
Prove the isolation point before the fix goes anywhere near it: the check is that the symptom changes when THAT point changes - a breakpoint or log at the boundary that shows the wrong lifetime, value or order, or the smallest edit that makes the failure move. A signature match that sends a fix at the wrong symbol is the failure this catalogue exists to prevent, so an unproven isolation point is stated as a hypothesis, never as the cause. Once the cause is proven, load the stack's house skill for the fix convention - your project's convention rules auto-attach it on a matching file touch. If the signature stays ambiguous after two passes, report the surviving hypotheses and what would decide between them rather than guessing.
1---2name: issue-signatures-runtime3description: "Use when a runtime failure needs a cause - a local or production stack trace, exception, hang, broken screen, NullReferenceException, NG0201. Not for red CI."4metadata:5 source: https://skillmd.com/skills/envoydev/issue-signatures-runtime6---78# Failure Signatures - what the crash means and where the cause actually lives910Every runtime failure has a signature, and the signature names where to look - which is almost never the line in the top frame. This is the single-chat form of the diagnoser seat's failure catalogue: match the evidence to a signature, then isolate at the place the signature points, not the place it threw. It pairs with `habits-root-cause` - the disciplined hypothesis-and-test loop; this one tells you which hypothesis the signature warrants. Read the evidence first and quote the exact frame, then match.1112## When to use1314Use when something breaks at runtime and you have the evidence - a stack trace, an exception, a hang or a broken screen, on your own machine or in a production event that carries the trace - and want to know where the real cause lives.1516Not for a CI or build/test-gate failure (the resolvers and the CI diagnoser own those). When the evidence spans more than one source, the gatherer fan-out below handles it; a run with a gate between every step is the user's gated investigation command.1718## The signatures - and where each isolates1920- **Null-reference / undefined access** (`NullReferenceException`, `Cannot read properties of undefined/null`). The frame names the dereference, but the cause is usually one hop up: a dependency never assigned, or a value read across an async gap before its `await` resolved (an `@Input` touched in the constructor before `ngOnInit`, a field read before the task that sets it finished). Isolate by walking the assignment of the null symbol, not the line that dereferenced it.21- **DI / composition-root failure** (`Unable to resolve service for type`, a startup `InvalidOperationException`, Angular `NG0201`). The injection site is innocent - the registration is missing, mis-scoped, or a captive dependency (a singleton capturing a scoped service). Isolate at the composition root (the container setup / module providers), never the consuming class.22- **Async deadlock / sync-over-async** (a hang, not a crash). `.Result` / `.Wait()` / `.GetAwaiter().GetResult()` blocking a captured synchronization context (the classic WPF / WinForms UI-thread and ASP.NET-request deadlock), or a `TaskCompletionSource` never completed. Isolate to the sync-over-async boundary, not the innermost `await`.23- **Race / shared mutable state** (reproduces under load or a specific ordering, passes in isolation). A `static` or singleton mutated concurrently, an un-awaited fire-and-forget, subscriptions firing out of order. Isolate by naming the shared cell and its competing writers, not by re-running until green.24- **Disposed / lifecycle** (`ObjectDisposedException`, `Cannot access a disposed context`). A `DbContext` or `HttpClient` captured past its scope, a subscription or timer firing after teardown, a handler outliving its view. Isolate to the lifetime boundary that ended early, not the use site.25- **Database contention / exhaustion** (a query that deadlocks, times out, or violates a constraint under concurrency but is fine in isolation). A deadlock victim (SQL Server error 1205, Postgres 'deadlock detected') from two transactions taking locks in opposite order; connection-pool exhaustion (a timeout acquiring a pooled connection - usually a leaked or un-disposed connection or `DbContext`, or sync-over-async starving the pool); or a unique / foreign-key violation surfacing a lost race. Isolate to the competing transactions and their lock order, or the connection that was never returned - not the statement that happened to lose.26- **Config / environment drift** (a value read as null or wrong, no crash at the read). A missing user secret / env var / `appsettings` key, a connection string pointing at the wrong database, a WPF binding silently no-op'ing (the `System.Windows.Data` error in the Output window). Isolate by proving the value the code actually received, not the value it expected.27- **Boundary / off-by-one** (`IndexOutOfRangeException`, `ArgumentOutOfRangeException`, an empty-sequence `.First()` / `.Single()`). A fencepost in a slice or loop, an empty collection assumed non-empty. Isolate to the boundary input that triggers it, and keep it as the regression case the fix must cover.28- **HTTP error with a clean response** (a returned status, no stack trace). Triage by the status class - it names the failing layer before you open a trace: 401 authentication, 403 authorization / policy, 400 / 422 validation, 404 routing / binding, 405 verb, an antiforgery or CORS-preflight rejection. Isolate at the layer the status names, not the handler body.2930## Execution modes3132This catalogue is single-sourced: the issue-diagnoser-runtime seat preloads this same file, so33the inline and seated forms never drift. Loaded INSIDE the seat, this section is already satisfied34- the seat is the dispatched form, and the rest of this section is not read there. Loaded in the35MAIN session, run the triage HERE and Read `references/gatherer-fan-out.md` before deciding on36evidence-gatherers - the inherit-or-ask rule, the four dispatch triggers, the stay-inline shapes37and a worked fan-out are that file. Either way, dispatch is explicit-only house-wide, so the seats38never start on your own say-so. Do NOT dispatch the diagnoser seat from this skill - the39signatures are already in context, so the seat would only duplicate them; the seat exists for the40orchestrated issue flow and direct @agent- calls, where it runs this same file in an isolated41context with the same gatherer fan-out.4243## How to use it4445Match the evidence to one signature, form the fewest hypotheses it warrants, and confirm each against located code before you touch anything - root cause before symptom, never a plausible guess. State the match in four lines - the quoted evidence, the signature, the isolation point and the hypothesis it warrants - plus the proof line once the check has run, then run the loop:4647```text48Evidence: 'ObjectDisposedException: Cannot access a disposed context instance' in OrderSyncJob.ExecuteAsync49Signature: disposed / lifecycle - a DbContext captured past its scope.50Isolate: the lifetime boundary - the scoped DbContext resolved once and stored on the singleton job - not the query line that threw.51Hypothesis: the singleton job stores the scoped DbContext it resolved at startup52Proof: <the log or breakpoint at the boundary, quoted> | unproven - <what would decide it>53```5455Prove the isolation point before the fix goes anywhere near it: the check is that the symptom changes when THAT point changes - a breakpoint or log at the boundary that shows the wrong lifetime, value or order, or the smallest edit that makes the failure move. A signature match that sends a fix at the wrong symbol is the failure this catalogue exists to prevent, so an unproven isolation point is stated as a hypothesis, never as the cause. Once the cause is proven, load the stack's house skill for the fix convention - your project's convention rules auto-attach it on a matching file touch. If the signature stays ambiguous after two passes, report the surviving hypotheses and what would decide between them rather than guessing.