Closed dudarboh closed 2 years ago
One possibility in this case could be to simply unset the CED_HOST
variable from within ced2go, when appropriate. This should be as simple as os.environ.pop('CED_HOST', None)
(where the default None
is just there to make sure that nothing breaks if it is not set). This would have to be done before the actual CEDViewer process is started. This also should leave the environment outside the python process of ced2go untouched.
CED_HOST
is taken from the environment here. So fixing this on a deeper level might be a bit more involved.
@tmadlener @gaede
Intro
One can use
ced2go
in two modes:n
argument:Issue
However if the environment variable
CED_HOST
is not empty, e.g. because it was specified in the.bashrc
for convenience The fully remote version, w/o-n
flag, still tries to connect to the$CED_HOST
and fails.Reproducible
with output:
Expected
It would be nice that if
n
flag is NOT specified it should ignore what is written in the env `$CED_HOST.