From 91b7873a889f1e8f9828d2d27d0339612a74ea48 Mon Sep 17 00:00:00 2001 From: Erik Darling <2136037+erikdarlingdata@users.noreply.github.com> Date: Thu, 18 Jun 2026 22:26:06 -0400 Subject: [PATCH] Remove dead FakeExecutor.UnforceFunc test seam (CS0649) The only build warning across the solution: UnforceFunc was read in UnforcePlanAsync but never assigned by any test, so it was always null (CS0649). Removed the field and its no-op invoke; UnforcePlanAsync returns the same default outcome as before. Solution now builds at 0 warnings. Co-Authored-By: Claude Opus 4.8 (1M context) --- Dashboard.Tests/RemediationTests.cs | 3 +-- 1 file changed, 1 insertion(+), 2 deletions(-) diff --git a/Dashboard.Tests/RemediationTests.cs b/Dashboard.Tests/RemediationTests.cs index e80dfad1..9d498b04 100644 --- a/Dashboard.Tests/RemediationTests.cs +++ b/Dashboard.Tests/RemediationTests.cs @@ -1943,7 +1943,6 @@ private sealed class FakeExecutor : IRemediationExecutor public bool AuditWriteResult = true; public Func? PreflightFunc; public Func? ForceFunc; - public Func? UnforceFunc; public int ForceCalls; public int UnforceCalls; @@ -1974,7 +1973,7 @@ public Task ForcePlanAsync(string database, long queryId, long public Task UnforcePlanAsync(string database, long queryId, long planId, RemediationIdentity identity, CancellationToken ct) { UnforceCalls++; - return Task.FromResult(UnforceFunc?.Invoke(database, queryId, planId) ?? new ForcePlanOutcome + return Task.FromResult(new ForcePlanOutcome { Database = database, QueryId = queryId, PlanId = planId, Status = RemediationStatus.Success, Forced = true, ExecutingLogin = "sa", GateSpid = 55, ExecSpid = 55