project deploy start exits 10 "fetch failed" when the connection closes between status checks; the deploy keeps running

Abierto
  • ¿Algo no está bien?
#3,685 2 comentarios 1 reacción 0 asignados Ver en GitHub

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
4/5
Tiempo estimado
3-5 días
Aptitud para principiantes
53/100
Tipo de issue
Error
Claridad
Bien especificado
Estado de actividad
Activo
Stack tecnológico
javascript, node.js
Área
cli, networking

Línea de trabajo

Start by reading source-deploy-retrieve's MetadataTransfer.isRetryableError and pollStatus path, then check the reported jsforce and undici error shapes. Reproduce the dropped connection with the CONNECT proxy described in the issue. Done when the deploy keeps polling after this transient failure and returns its final result; add coverage for the retryable error if the repository has relevant tests.

Escrito por el modelo de indexación a partir del texto del issue.

Descripción

bug
Before You Submit
  • I'm using the latest version of Salesforce CLI (reproduced on 2.157.8)
  • I've searched the existing issues (related: #3622, which is about HTTP/2 crashes in data commands; this one is HTTP/1.1 and handled, but not retried)
Command

sf project deploy start (also deploy validate, deploy quick: any command that waits with MetadataApiDeploy.pollStatus)

Org Type

Sandbox

Did this work before?

Not sure

Summary

When Salesforce closes the HTTP connection between two deploy status checks, sf project deploy start --wait N exits 10 with MetadataTransferError: Metadata API request failed: fetch failed, while the deploy keeps running and later succeeds in the org. In CI this marks a successful deploy as failed.

Cause, as far as we can read the code:

  • jsforce-node's fetchWithRetries retries only GET/PUT/HEAD/OPTIONS/DELETE; checkDeployStatus is a SOAP POST, so the request is not retried.
  • source-deploy-retrieve MetadataTransfer.isRetryableError tolerates network errors by matching error.message against ECONNRESET, socket hang up, etc. With undici the message is fetch failed (the cause, SocketError: other side closed, UND_ERR_SOCKET, is in error.cause), so none match and poll() rethrows. Same list in SDR 13.6.0 and 13.12.0.

We saw it 4 times in 20 minutes, from two different machines (GitHub Actions runners and a cloud VM), against the same sandbox, with no Trust incident.

Steps to reproduce

The closure is intermittent; we reproduce it deterministically with a local CONNECT proxy that closes the tunnel of one status check:

  1. Run a CONNECT proxy on 127.0.0.1:18081 that, after ~20 s, closes the next tunnel right after the client sends its request (about 20 lines of Node net; happy to share).
  2. HTTPS_PROXY=http://127.0.0.1:18081 sf project deploy start --dry-run --source-dir force-app/main/default/classes -o <sandbox> --test-level RunSpecifiedTests --tests SomeTest --wait 10 --json
Expected Result

The CLI treats the closed connection as a transient network error (as it does for ECONNRESET), keeps polling, and returns the deploy's final result (exit 0 here).

Actual Result

Exit 10 after the first closed connection:

{"status":10,"name":"MetadataTransferError","message":"Metadata API request failed: fetch failed","data":{"id":"0Af..."}}

The CLI log (~/.sf/sf-YYYY-MM-DD.log) has:

TypeError: fetch failed
    at Object.processResponse (undici/lib/web/fetch/index.js:272:16)
    at async fetchWithRetries (@jsforce/jsforce-node/lib/request.js:111:25)
caused by: SocketError: other side closed
    at TLSSocket.onHttpSocketEnd (undici/lib/dispatcher/client-h1.js:1024:22)

sf project deploy report --job-id <id> afterwards shows the job Succeeded.

Suggested fix

In isRetryableError, also inspect error.cause (and error.cause.cause) for code in UND_ERR_SOCKET, ECONNRESET, ETIMEDOUT, …, or add fetch failed / other side closed to retryableErrors. A status check is read-only, so retrying it is safe.

Our workaround: when the command exits 10 with this error and data.id, we follow the same job with sf project deploy report --job-id <id> --wait <remaining>.

System Information
@salesforce/cli/2.157.8 linux-x64 node-v24.22.2
@salesforce/source-deploy-retrieve 13.11.0, @jsforce/jsforce-node 3.12.0, undici 8.12.3
(also @salesforce/cli 2.156.5: SDR 13.6.0, undici 8.12.2)
Lenguaje dominante
Sin datos de lenguaje
Estrellas
575
Forks
80
Merge medio
5 h 58 min
PR fusionados (30 d)
4

Preparar el entorno

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de forcedotcom/cli

Todos los issues de forcedotcom/cli

Issues similares

Más issues de CLI

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.