Repository navigation
fix(cloud): align CloudApp proxy selection with VeFaaS SDK - #1143
Merged
Merged
Conversation
yaozheng-fang
approved these changes
Sep 22, 2026
PolarisCzh
pushed a commit
to PolarisCzh/veadk-python
that referenced
this pull request
Sep 29, 2026
…e#1143) Co-authored-by: TRAE CLI <traecli@bytedance.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Cloud resource deployment can succeed and then fail when CloudApp initializes HTTPX, because HTTPX validates proxy settings that the VeFaaS SDK never uses. For example, an unrelated
ALL_PROXY=socks://127.0.0.1:7897raises an error after the application has already been released.Align CloudApp with the VeFaaS SDK by selecting the HTTP(S) proxy for its endpoint, preferring the uppercase environment variable and falling back to lowercase. An explicit HTTPX transport prevents additional environment or system proxy discovery while preserving certificate configuration. As with the SDK,
ALL_PROXYandNO_PROXYare not applied; an invalid selected proxy still fails.Validation:
pre-commit run --files veadk/cloud/cloud_app.py tests/cloud/test_cloud_app_proxy.pypassedpython -m pytest tests/cloud/test_cloud_app_proxy.py tests/test_cloud.py -q: 62 passed