rusackas opened a new pull request, #40874: URL: https://github.com/apache/superset/pull/40874
### SUMMARY The `docker-build` job is the single biggest source of `master` CI flakiness — it failed **~25% of runs (8/32)** over the last few days, recurring across multiple days. Almost every failure is the same transient: ``` #15 [linux/arm64 build 4/4] RUN npm ci && npm run build #15 49.22 npm error code ECONNRESET #15 49.23 npm error network read ECONNRESET #15 ERROR: process "/bin/sh -c npm ci && npm run build" did not complete successfully: exit code: 152 ``` `npm ci` runs with npm's default fetch-retry settings and no wrapper, so a single dropped connection to the npm registry fails the entire multi-platform build. This PR sets npm's fetch-retry configuration via environment variables immediately before `npm ci` in both Dockerfiles (`Dockerfile`, and `superset-websocket/Dockerfile` build + prod stages): - `npm_config_fetch_retries=5` (default 2) - `npm_config_fetch_retry_mintimeout=20000` (default 10000) - `npm_config_fetch_retry_maxtimeout=120000` (default 60000) - `npm_config_fetch_timeout=600000` (default 300000) These are no-ops on the happy path and only engage when the registry blips. Verified the env-var mapping is honored: `npm_config_fetch_retries=5 npm config get fetch-retries` → `5`. ### BEFORE/AFTER SCREENSHOTS OR ANIMATED GIF N/A — CI/build resilience change. ### TESTING INSTRUCTIONS The image build is exercised by the existing `docker-build` matrix in CI. No behavior change to the produced image; only npm's retry/backoff during dependency install. ### ADDITIONAL INFORMATION - [ ] Has associated issue: - [ ] Required feature flags: - [ ] Changes UI - [ ] Includes DB Migration - [ ] Introduces new feature or API - [ ] Removes existing feature or API 🤖 Generated with [Claude Code](https://claude.com/claude-code) -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
