Title: [BUG]: Proxy startup may report success when retries are exhausted and process does not stabilize · Issue #3530 · github/codeql-action · GitHub
Open Graph Title: [BUG]: Proxy startup may report success when retries are exhausted and process does not stabilize · Issue #3530 · github/codeql-action
X Title: [BUG]: Proxy startup may report success when retries are exhausted and process does not stabilize · Issue #3530 · github/codeql-action
Description: Problem The proxy startup logic in start-proxy-action.ts can report successful initialization even when the proxy process fails to stabilize after retry attempts. The previous implementation: Retries on spawn or early exit Only throws on...
Open Graph Description: Problem The proxy startup logic in start-proxy-action.ts can report successful initialization even when the proxy process fails to stabilize after retry attempts. The previous implementation: Retri...
X Description: Problem The proxy startup logic in start-proxy-action.ts can report successful initialization even when the proxy process fails to stabilize after retry attempts. The previous implementation: Retri...
Opengraph URL: https://github.com/github/codeql-action/issues/3530
X: @github
Domain: github.com
{"@context":"https://schema.org","@type":"DiscussionForumPosting","headline":"[BUG]: Proxy startup may report success when retries are exhausted and process does not stabilize","articleBody":"## Problem\n\nThe proxy startup logic in `start-proxy-action.ts` can report successful initialization even when the proxy process fails to stabilize after retry attempts.\n\nThe previous implementation:\n\n* Retries on spawn or early exit\n* Only throws on immediate spawn errors\n* Does not explicitly fail when all retry attempts are exhausted\n* May proceed with outputs set despite no stable process remaining alive\n\nThis can lead to false-positive startup.\n\n## Impact\n\nWhen startup silently fails:\n\n* Downstream steps may fail with opaque dependency or networking errors\n* Failures manifest later in the workflow\n* Root cause becomes difficult to diagnose\n\nInstead of failing fast during initialization, workflows continue in a degraded state.\n\n## Expected Behavior\n\nIf the proxy fails to stabilize after retry attempts, startup should fail explicitly with a clear diagnostic error.\n\n## Proposed Solution\n\n* Detect retry exhaustion explicitly\n* Throw a clear error including the last exit code\n* Verify process remains alive after stabilization delay\n* Retry using a new ephemeral port before terminal failure\n* Extract startup logic into a dedicated launcher module for testability\n\nThis preserves existing outputs, telemetry behavior, and wrapper semantics while preventing silent failure.","author":{"url":"https://github.com/iaadillatif","@type":"Person","name":"iaadillatif"},"datePublished":"2026-03-01T18:50:40Z","url":"https://github.com/github/codeql-action/issues/3530"}
| react-profiling | 0 |
| react-import-map | react,react-dom,react-dom/client,react-dom/profiling,react-is,react-reconciler,react/compiler-runtime,react/jsx-dev-runtime,react/jsx-runtime,scheduler@d5750093facf |
| route-pattern | /_view_fragments/issues/show/:user_id/:repository/:id/issue_layout(.:format) |
| route-controller | voltron_issues_fragments |
| route-action | issue_layout |
| fetch-nonce | v2:0475c6f5-8bb0-03e1-5cfc-c6bb4ef79039 |
| current-catalog-service-hash | 81bb79d38c15960b92d99bca9288a9108c7a47b18f2423d0f6438c5b7bcd2114 |
| request-id | B2F4:2B6F5F:2C8945D:3EBF1E6:6AED2B27 |
| html-safe-nonce | 4e2baa9653819a40ff508e48c8e03e39cd3aa6a2382aa39ceac836d967d5533e |
| visitor-payload | eyJyZWZlcnJlciI6IiIsInJlcXVlc3RfaWQiOiJCMkY0OjJCNkY1RjoyQzg5NDVEOjNFQkYxRTY6NkFFRDJCMjciLCJ2aXNpdG9yX2lkIjoiMTUxMzg3NTU2NTg4ODQ4MjA4NyIsInJlZ2lvbl9lZGdlIjoiaWFkIiwicmVnaW9uX3JlbmRlciI6ImlhZCJ9 |
| visitor-hmac | d8d11f78e53bca0d3b1556066721ea2ff075e921a8bb71d82746138f2f8add81 |
| hovercard-subject-tag | issue:4007995982 |
| github-keyboard-shortcuts | repository,issues,copilot |
| google-site-verification | Apib7-x98H0j5cPqHWwSMm6dNU4GmODRoqxLiDzdx9I |
| octolytics-url | https://collector.github.com/github/collect |
| analytics-location | / |
| fb:app_id | 1401488693436528 |
| apple-itunes-app | app-id=1477376905, app-argument=https://github.com/_view_fragments/issues/show/github/codeql-action/3530/issue_layout |
| twitter:image | https://opengraph.githubassets.com/51fda132931dff9d42180af7a7576cf2682ea2fc8e98e38dd1acd22d2abdcde5/github/codeql-action/issues/3530 |
| twitter:card | summary_large_image |
| og:image | https://opengraph.githubassets.com/51fda132931dff9d42180af7a7576cf2682ea2fc8e98e38dd1acd22d2abdcde5/github/codeql-action/issues/3530 |
| og:image:alt | Problem The proxy startup logic in start-proxy-action.ts can report successful initialization even when the proxy process fails to stabilize after retry attempts. The previous implementation: Retri... |
| og:image:width | 1200 |
| og:image:height | 600 |
| og:site_name | GitHub |
| og:type | object |
| og:author:username | iaadillatif |
| hostname | github.com |
| expected-hostname | github.com |
| None | 9d95365dda0576efe9b71f45807595e396bd0ca9286fba5367a05048e6ddf8f2 |
| turbo-cache-control | no-preview |
| go-import | github.com/github/codeql-action git https://github.com/github/codeql-action.git |
| octolytics-dimension-user_id | 9919 |
| octolytics-dimension-user_login | github |
| octolytics-dimension-repository_id | 259445878 |
| octolytics-dimension-repository_nwo | github/codeql-action |
| octolytics-dimension-repository_public | true |
| octolytics-dimension-repository_is_fork | false |
| octolytics-dimension-repository_network_root_id | 259445878 |
| octolytics-dimension-repository_network_root_nwo | github/codeql-action |
| turbo-body-classes | logged-out env-production page-responsive |
| disable-turbo | false |
| browser-stats-url | https://api.github.com/_private/browser/stats |
| browser-errors-url | https://api.github.com/_private/browser/errors |
| release | 98b41fa4b5635ceb45a4c54320fced73817ff290 |
| ui-target | full |
| theme-color | #1e2327 |
| color-scheme | light dark |
| react-app-name | issues |
Links:
Viewport: width=device-width