fix: clarify invalid container root errors - #2116
Conversation
|
@efegokdemir Also can you please cryptographically sign the commits? thanks |
0af6232 to
1088dbc
Compare
|
Inlined the container-root lookup error and invalid-root checks directly in |
ded8b53 to
45652aa
Compare
|
@henry118 The requested cleanup is on the existing branch: the helper was inlined, the extra test file was removed, and the contributor commits were rewritten with verified cryptographic signatures. DCO is passing and the focused update-ldcache tests were run. Please re-review when available. |
Signed-off-by: Efe Gökdemir <gokdemirefe1903@gmail.com>
45652aa to
c06d8ee
Compare
|
/ok to test c06d8ee |
Coverage Report for CI Build 36918093826Warning Build has drifted: This PR's base is out of sync with its target branch, so coverage data may include unrelated changes. Coverage decreased (-0.01%) to 44.26%Details
Uncovered Changes
Coverage Regressions1 previously-covered line in 1 file lost coverage.
Coverage Stats
💛 - Coveralls |
Summary
The update-ldcache hook used one error branch for OCI root lookup failures and invalid root values, producing a misleading
<nil>suffix for empty or/roots. The cases are now split, lookup failures preserve their cause, and invalid roots are reported explicitly.Changes
run, per maintainer feedback.GetContainerRoot()failure with%w./roots as explicit invalid-root errors.Validation
gofmt -w cmd/nvidia-cdi-hook/update-ldcache/update-ldcache.gogo test ./cmd/nvidia-cdi-hook/update-ldcache— passedgo vet ./cmd/nvidia-cdi-hook/update-ldcache— passedgo build ./cmd/nvidia-cdi-hook/update-ldcache— passedgit diff --check— passedThe PR has one contributor commit, GitHub reports it as Verified, and the Golang and CodeQL checks are green.
Issue
Fixes #2115