Concurrency and State Risk
Detects async void methods, blocking async calls (.Result, .Wait()), static mutable state, and patterns that introduce deadlock risk.
Why this rule exists
async void cannot be awaited and crashes the process on unhandled exceptions. .Result on the request thread deadlocks under load. Static mutable state corrupts under parallel requests. All three pass unit tests and fail in production.
Code example
+ public async void HandleClick() { await SaveAsync(); }
+ var data = httpClient.GetStringAsync(url).Result;+ public async Task HandleClickAsync() { await SaveAsync(); }
+ var data = await httpClient.GetStringAsync(url);Configuration
Disable or adjust the severity of this rule in .gauntletci.json:
{
"rules": {
"GCI0016": { "enabled": true, "severity": "Block" }
}
}See Configuration for the full schema.
Related rules
Resource Lifecycle
Detects disposable resources allocated without a using statement or try/finally disposal, leading to connection and handle leaks.
External Service Safety
Detects unsafe HTTP client usage and external service call patterns that lack timeout, cancellation, or retry configuration.
Pattern Consistency Deviation
Detects mixed sync/async naming conventions and service locator anti-patterns introduced inconsistently within the same file.
Discussed in
Real-world evidence
Implemented in src/GauntletCI.Core/Rules/Implementations/GCI0016_*.cs.
Eric Cogen -- Founder, GauntletCI
Twenty years in .NET production. Most of those years, the bugs that hurt me were not the ones tests caught. They were the assumptions I did not know I was making: a removed guard clause, a renamed method that still did the old thing, a catch {} that turned a page into a silent dashboard lie. GauntletCI is the checklist I wish I had run before every commit. It runs the rules I learned the hard way, so you do not have to.