Overview

7 days30 days

Latest CI Pipeline Executions

Fuzzy

Failed
36651
Flaky task→
47c2b69d docs(misc): describe the remote cache download timeout as stall detection [Self-Healing CI Rerun]
by nx-cloud[bot]
Failed
36651
Flaky task→
6b9c5a94 docs(misc): describe the remote cache download timeout as stall detection [Self-Healing CI Rerun]
by nx-cloud[bot]
Failed
36651
Flaky task→
8292a799 docs(misc): describe the remote cache download timeout as stall detection [Self-Healing CI Rerun]
by nx-cloud[bot]
Failed
36651
Flaky task→
8292a799 docs(misc): describe the remote cache download timeout as stall detection [Self-Healing CI Rerun]
by nx-cloud[bot]
Succeeded
36651
6f856171 docs(misc): describe the remote cache download timeout as stall detection The previous wording, "a 30 second timeout on downloads", reads as a total budget for the transfer and invites users to disable timeouts over a misunderstanding. It bounds the wait for the next chunk and resets on each one, so say that, and name the one case where the budget really does apply as a single deadline: before the server sends its first byte. Splits the fatal/non-fatal material into its own paragraph rather than trailing a longer one. Claude-Session: https://claude.ai/code/session_0198BaKdjofDvkjoQKitCjEX
by Craigory C...
Failed
36651
Flaky task→
6f856171 docs(misc): describe the remote cache download timeout as stall detection The previous wording, "a 30 second timeout on downloads", reads as a total budget for the transfer and invites users to disable timeouts over a misunderstanding. It bounds the wait for the next chunk and resets on each one, so say that, and name the one case where the budget really does apply as a single deadline: before the server sends its first byte. Splits the fatal/non-fatal material into its own paragraph rather than trailing a longer one. Claude-Session: https://claude.ai/code/session_0198BaKdjofDvkjoQKitCjEX
by Craigory C...
Succeeded
36651
21f335b2 chore(core): expect a warning, not an error, when the remote cache server is down The http remote cache e2e tests still asserted the pre-#36651 behaviour: that an unreachable cache server fails the build and prints its URL. Remote cache failures are now non-fatal, so the build succeeds with a cache miss and the failure is surfaced through handleRemoteCacheError()'s output.warn() instead. Assert that warning and the successful build rather than the old hard error. Only the errors isFatalRemoteCacheError() recognises still stop a run, and those keep their existing coverage in the sibling unauthorized-token test. Both cache.test.ts and cache-no-daemon.test.ts carry the same case.
by Craigory C...
Failed
36651
Fix applied→
bdbe1725 docs(misc): document remote cache timeouts and incomplete uploads ## Current Behavior The self-hosted caching spec describes `Content-Length` as "The file size in bytes" without stating that a server must validate it, and says nothing about what should happen when a `PUT` stops early. Nothing documents the client's timeout behavior or which cache failures are fatal. ## Expected Behavior The `Content-Length` parameter now states that servers must compare received bytes against it and reject short uploads, and a new "Handling incomplete uploads" section explains why: a truncated artifact left readable is worse than a cache miss, because `409 Conflict` means Nx cannot replace that entry on a later upload. That section also breaks down when this is a risk. Servers that buffer the whole body before the handler runs are largely safe by default, because the framework raises a request-aborted error and the handler never runs. Servers that stream the body to storage must check the copy's error, since bytes are already persisted by the time truncation is detected. Two ordering rules matter more than the language: write the artifact durably before publishing the entry, and remember that for filesystem-backed servers the artifact path is itself the index. Reverse-proxy buffering is called out, since nginx's `proxy_request_buffering` defaults to on and is commonly disabled for large uploads. The usage notes document the connect, download and upload timeouts, the fact that a failed or timed-out cache request degrades to a local rebuild rather than failing the run, and the exceptions that still stop it. The environment variable reference gains `NX_SELF_HOSTED_REMOTE_CACHE_NO_TIMEOUTS`. ## Related Issue(s) Supports #36640, #36107 and #36036.
by Craigory C...
Failed
36651
Fix ready→
bdbe1725 docs(misc): document remote cache timeouts and incomplete uploads ## Current Behavior The self-hosted caching spec describes `Content-Length` as "The file size in bytes" without stating that a server must validate it, and says nothing about what should happen when a `PUT` stops early. Nothing documents the client's timeout behavior or which cache failures are fatal. ## Expected Behavior The `Content-Length` parameter now states that servers must compare received bytes against it and reject short uploads, and a new "Handling incomplete uploads" section explains why: a truncated artifact left readable is worse than a cache miss, because `409 Conflict` means Nx cannot replace that entry on a later upload. That section also breaks down when this is a risk. Servers that buffer the whole body before the handler runs are largely safe by default, because the framework raises a request-aborted error and the handler never runs. Servers that stream the body to storage must check the copy's error, since bytes are already persisted by the time truncation is detected. Two ordering rules matter more than the language: write the artifact durably before publishing the entry, and remember that for filesystem-backed servers the artifact path is itself the index. Reverse-proxy buffering is called out, since nginx's `proxy_request_buffering` defaults to on and is commonly disabled for large uploads. The usage notes document the connect, download and upload timeouts, the fact that a failed or timed-out cache request degrades to a local rebuild rather than failing the run, and the exceptions that still stop it. The environment variable reference gains `NX_SELF_HOSTED_REMOTE_CACHE_NO_TIMEOUTS`. ## Related Issue(s) Supports #36640, #36107 and #36036.
by Craigory C...
Failed
36651
Fix ready→
bdbe1725 docs(misc): document remote cache timeouts and incomplete uploads ## Current Behavior The self-hosted caching spec describes `Content-Length` as "The file size in bytes" without stating that a server must validate it, and says nothing about what should happen when a `PUT` stops early. Nothing documents the client's timeout behavior or which cache failures are fatal. ## Expected Behavior The `Content-Length` parameter now states that servers must compare received bytes against it and reject short uploads, and a new "Handling incomplete uploads" section explains why: a truncated artifact left readable is worse than a cache miss, because `409 Conflict` means Nx cannot replace that entry on a later upload. That section also breaks down when this is a risk. Servers that buffer the whole body before the handler runs are largely safe by default, because the framework raises a request-aborted error and the handler never runs. Servers that stream the body to storage must check the copy's error, since bytes are already persisted by the time truncation is detected. Two ordering rules matter more than the language: write the artifact durably before publishing the entry, and remember that for filesystem-backed servers the artifact path is itself the index. Reverse-proxy buffering is called out, since nginx's `proxy_request_buffering` defaults to on and is commonly disabled for large uploads. The usage notes document the connect, download and upload timeouts, the fact that a failed or timed-out cache request degrades to a local rebuild rather than failing the run, and the exceptions that still stop it. The environment variable reference gains `NX_SELF_HOSTED_REMOTE_CACHE_NO_TIMEOUTS`. ## Related Issue(s) Supports #36640, #36107 and #36036.
by Craigory C...