Repository navigation
fix(go): give vulnerability scans bounded swap headroom - #950
Conversation
Prepare and verify an owned 4 GiB swap file before symbol analysis, retain the existing deadlines and finding gate, and retire only the owned file afterward. Add refusal controls and native Linux activation proof. Part of #671; historical runner-loss attribution remains open.
Code coverage overviewLanguages: Go, C# Go / code-coverage/test
C# / code-coverage/dotnet
Go / code-coverage/go
ℹ️ Calculations represent line coverage. Results may change as calculations are updated. Updated |
Validation at
Correctness and simplification review found no further issue. The scan mode, finding evaluator, 24-minute attempts, timeout-only retry and 60-minute job ceiling remain unchanged. CI is still running, so no external review is requested yet and this remains draft. Native setup success alone will not prove the KSail runner interruption repaired or attribute historical losses; #671 stays open. |
Use the raw byte-sized swapon table for the native kernel assertion. The runner does not support JSON output. Part of #950.
Fixed the native test at Local validation passed: swap lifecycle and failure controls, ShellCheck, scanner memory controls, timeout and immutable scanner wiring checks, manifest rendering, all 15 repository baseline checks, and diff whitespace checks. Hosted proof now passed at this head: CI run 43797444530, native job 133069550714 verified real kernel activation, size, private mode and cleanup. All observed checks are settled without failures, and CodeRabbit completed a finding-free review of this exact head. This remains draft: final required-gate verification is incomplete. #671 stays open for bounded interruption attribution; native swap setup proof does not establish the cause of historical runner losses or consumer adoption. |
@coderabbitai review |
Action performed
|
|
No actionable comments were generated in the recent review. Walkthrough
Merge Risk:
|
Revalidated As a workflow user, I read CI run 43797444530, native job 133069550714 at this exact head and its filtered output: the real Linux kernel activated the owned swap, verified its private mode, and retired it; preparation failures and insufficient disk were rejected. This demonstrates the swap lifecycle. It does not establish historical runner-loss causality or an affected-consumer scan. The only unobservable gate is |
Why
Repeated runner interruptions leave KSail's security validation unfinished and hold up delivery. Successful scans already approach the runner's memory ceiling.
What
Give the scanner bounded temporary swap headroom and verify its cleanup. Security findings still fail validation; hosted proof and KSail adoption remain required before this can count as a repair.
Part of #671