Retry npm ci through the runner's transfer corruption

CIkamo-marketing
Ya
20 Agosti 2026, 05:48 UTC
Mwandishi
Kamo
Ahadi ya
160a9c7

The build failed on: npm error code ERR_SSL_CIPHER_OPERATION_FAILED ossl_gcm_stream_update:cipher operation failed That is a GCM authentication-tag mismatch — bytes arrived altered, TLS refused them, npm aborted. Nothing to do with the lockfile or the registry; it is transfer corruption on the local link, the same class this runner has produced before, and the identical command succeeds on the next attempt. npm's own `fetch-retries` does not help because the failure takes down the process rather than a single request. So `npm ci` is retried up to five times with a widening backoff, clearing the cache between attempts so a partially written, corrupt tarball cannot simply be replayed from disk. The trailing `exit 1` is the part worth keeping honest: without it an install that failed every attempt would leave the layer green and resurface much later as a missing module at build or runtime. Verified the loop with a stubbed npm rather than by reading it — succeeds mid-loop and exits 0, exhausts all five and exits 1.

Mabadiliko yote

Je, unaona nini kuhusu usafiri?

Kila moja ya hizi updates ardhi katika nafasi yako ya kazi moja kwa moja. Kuanza bure na kuangalia kukua wiki baada ya wiki.

Kuwa Huru MileleMtazamo wa bei