proxy issue: log in time out #117
Comments
|
@shaoxul Hmm, I have not met this problem before. But just found that the VS Code has proxy related settings. Maybe you can have a try?
|
|
@jdneo Thank you for your reply. Yes, I tried, but it works for the VS code itself(e.g. extension market), but not works for this this extension. |
|
So far, I have no idea what I can do for your problem... Need some more investigation here... |
|
@shaoxul I have met the same problem as you. |
|
same problem |
…ode-OpenSource#117) We use leetcode-cli and leetcode-cli uses request to call LeetCode web API. It's lucky that request respects the http proxy env variables(http_proxy, https_proxy), so all we need to do is passing proxy as env variable http_proxy to every command. TODO: do we need to set https_proxy for https request?
…ode-OpenSource#117) We use leetcode-cli and leetcode-cli uses request to call LeetCode web API. It's lucky that request respects the http proxy env variables(http_proxy, https_proxy), so all we need to do is passing proxy as env variable http_proxy to every command. TODO: do we need to set https_proxy for https request?
|
@edvardchen Provided a solution in #147. Root CauseThe root cause is that when we trigger a leetcode-cli command, we will spawn a new child_process to send the request, which may bypass the proxy setting in VS Code. SolutionSo, we need to read the proxy setting of VS Code. and set it in the created child_process. New BehaviorNow the extension should honor the proxy setting in VS Code More details can be found in #147. And the fix will be released in 0.11.0 |
Dear friends,
For the sake of the gateway firewall, the http proxy must be used to connect internet.
But the log-in always times out. It looks like to try to connect to the leetcode server directly instead of through the proxy.
Is there any configuration I missed?
The text was updated successfully, but these errors were encountered: