Repository navigation
fix(kubescape): recover stuck vulnerability summaries - #5402
Conversation
Part of #4263. Reconcile an intact summary payload with lagging metadata before startup and on scanner retries. Preserve payloads and scan times, condition writes on the exact observed row, and refuse unsafe identities, paths or versions. Prove retention, retries, cancellation and failure boundaries with real SQLite and filesystem tests; run the full storage package with race detection before image publication.
@coderabbitai review |
|
|
Warning Review limit reachedYou've used all free OSS reviews for now. Wait for the free limit to reset to keep reviewing this public repository. Next included review available in 37 minutes. View limit details
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
@codex review |
Codex Review SummaryThis comment shows the latest Codex review activity on this pull request.
ℹ️ About Codex in GitHubYour team has set up Codex to review pull requests in this repo. Reviews are triggered when you
Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings. |
|
Codex Review: Didn't find any major issues. Keep it up! Reviewed commit: ℹ️ About Codex in GitHubYour team has set up Codex to review pull requests in this repo. Reviews are triggered when you
If Codex has suggestions, it will comment; otherwise it will react with 👍. Codex can also answer questions or update the PR. Try commenting "@codex address that feedback". |
Readiness at Hosted source verification run 40416583890 applied all three patches to the pinned upstream source, passed the complete race suite and built the Linux compatibility image without publication. The CI run passed its selected checks, including manifest validation and regressions. Codex's current-head review reports no findings; the full thread census is empty. The forge reported CLEAN and mergeable at this head. Required-gate discovery confirms the reported gates; configured native This delivers the tested producer repair and publisher. Production adoption remains a separate immutable image-pin change after signed publication, recovery evidence rebind and review. Neither deployment nor complete scan coverage is claimed here; #4263 remains open for live acceptance and remaining gaps. |
Why
Vulnerability results can become stuck after a failed save, leaving the scanner unable to refresh the information used for security decisions.
What
Adds a repair that preserves existing scan records and rejects ambiguous changes. Deployment remains gated on signed publication and a separate verified rollout.
Part of #4263