Skip to content

fix(proxy): propagate noProxy on startup and UI reload#274

Open
snvtac wants to merge 1 commit into
OpenBMB:mainfrom
snvtac:snvtac/253-proxy-no-proxy-cold-start
Open

fix(proxy): propagate noProxy on startup and UI reload#274
snvtac wants to merge 1 commit into
OpenBMB:mainfrom
snvtac:snvtac/253-proxy-no-proxy-cold-start

Conversation

@snvtac

@snvtac snvtac commented Jun 23, 2026

Copy link
Copy Markdown

Summary

  • Pass proxy.noProxy into the CLI cold-start proxy installer.
  • Export NO_PROXY and no_proxy for the UI runtime env when a proxy URL is configured.
  • Reapply the UI server's global proxy dispatcher on config reload and clear/restore config-managed proxy env vars when proxy config is removed.

Root cause

proxy.noProxy was stored in config and respected by the CLI hot-reload path, but the cold-start call only passed proxy.url. The UI runtime env also exported only HTTPS_PROXY / https_proxy, so spawned UI runtime processes did not receive the configured bypass list. During review, the reload path also needed cleanup so removed proxy settings do not leave stale env vars or dispatcher state behind.

Closes #253.

Validation

  • npm test
  • pnpm --dir ui test pilotdeckConfig.test.js pilotdeckConfigReloader.test.js

Note: I also ran pnpm --dir ui test; it currently fails in unrelated existing streaming/session tests (streamSmoother.test.ts and useSessionStore.streaming.test.ts) that are outside this PR's touched files.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

bug(proxy): proxy.noProxy is ignored on cold start and UI runtime env

1 participant