stacklok / toolhive / 24716398765

66%

Build Type

push

github

Committed by web-flow

Commit Message

Return 502 Bad Gateway when OCI skill pull fails (#4956)

* Return 502 Bad Gateway when OCI content pull fails

getContentFromOCI previously mapped registry.Pull failures to 400 Bad Request, but auth errors, unreachable registries, missing manifests, and network timeouts are upstream failures the caller cannot fix by changing their input. Align with getContentFromGit, which already returns 502 Bad Gateway for git resolve failures, so clients see consistent semantics across both backends.

* Return 502 Bad Gateway when OCI install pull fails

installFromOCI previously mapped registry.Pull failures to 400 Bad Request, which incorrectly blamed the caller for upstream registry problems (auth, network, manifest unknown). Return 502 Bad Gateway to match the behaviour just applied to GetContent and the existing git install path.

Coverage Stats

2 of 2 new or added lines in 2 files covered. (100.0%)

4 existing lines in 2 files now uncovered.

58307 of 87772 relevant lines covered (66.43%)

62.34 hits per line