Closed wattse closed 2 years ago
Thanks for the report (and apologies for the delay). I've been doing some issue pruning here so that genuine issues like yours will bubble to the top.
I don't have an easy way to reproduce this. Can someone else give it a shot?
@mcg1969 I'm also having the same problem because I'm using constructor
in a company where all the HTTP access is behind proxies. To reproduce this simply execute conda config --set proxy_servers.no_proxy https://foo/
and then invoke constructor
. It's easy to observe if you have two breakpoints in the main
function of fcp.py
module, one before, and after the call to the context manager:
print(f"before: {conda_context.proxy_servers}") # good
breakpoint() # or import pdb; pdb.set_trace()
with env_vars({
"CONDA_PKGS_DIRS": download_dir,
}, conda_replace_context_default):
print(f"after: {conda_context.proxy_servers}") # bad (blanked out)
breakpoint() # or import pdb; pdb.set_trace()
Also, my .condarc
has a configuration for ssl_verify
pointing to a .pem
file in disk. Before the context manager that value is correctly set in the conda_context
, containing the path to the file, but inside the context manager that value is lost and replaced with boolean True
, which also causes problems.
Thanks for the fix @gabrielcnr !
Hi there, thank you for your contribution!
This issue has been automatically marked as stale because it has not had recent activity. It will be closed automatically if no further activity occurs.
If you would like this issue to remain open please:
NOTE: If this issue was closed prematurely, please leave a comment.
Thanks!
I'm attempting to use constructor v3, but it fails to use proxy settings specified in my .condarc file. I'm running on win64, conda version is 4.7.12, constructor version is 3.0.
The initial error messages were the standard proxy warning messages:
I placed some debug print statements in CondaSession (conda/gateways/connection/session.py) to check if the proxy information is passing through with constructor. It isn't. The same debug print statements work for a standard conda install command, correctly providing
as the relevant proxy interfaces (cntlm). For a constructor call, the output is
Somewhere, constructor is ignoring some of the .condarc settings. I'm currently forcing my proxy settings in a conda env to make this work by editing conda/gateways/connection/session.py, line 67ish: