Toolshed unwanted version downgrade on Windows

[Tristan Croll]

The following bug report has been submitted:
Platform:        Windows-10-10.0.18362
ChimeraX Version: 0.91 (2019-11-21)
Description
Lately I get the following odd behaviour when building Clipper for Windows (only in Windows), where it builds and installs the new version, then immediately downgrades back to the old version.

"c:\Program Files\ChimeraX\bin\python.exe" "c:\Program Files\ChimeraX-daily\ChimeraX\bin\Lib\site-packages\ChimeraX_main.py" --nogui --cmd "devel clean .; devel install .; exit"

...
...
removing build\bdist.win-amd64\wheel
Distribution is in .\dist\ChimeraX_Clipper-0.9.11-cp37-cp37m-win_amd64.whl
Executing: toolshed install ".\\dist\\ChimeraX_Clipper-0.9.11-cp37-cp37m-win_amd64.whl"
Successfully installed ChimeraX-Clipper-0.9.11
Installed ChimeraX-Clipper (0.9.10)

Executing: exit
Exiting ...

Log:
UCSF ChimeraX version: 0.91 (2019-11-21)  
© 2016-2019 Regents of the University of California. All rights reserved.  
How to cite UCSF ChimeraX  




OpenGL version: 3.3.0 NVIDIA 426.00
OpenGL renderer: GeForce GTX 1070/PCIe/SSE2
OpenGL vendor: NVIDIA Corporation

[Tristan Croll]

Just needing to clarify - the execution string I use is actually:

"c:\Program Files\ChimeraX-daily\ChimeraX\bin\python.exe" "c:\Program Files\ChimeraX-daily\ChimeraX\bin\Lib\site-packages\ChimeraX_main.py" --nogui --cmd "devel clean .; devel install .; exit"

(that is, the python executable and ChimeraX_main.py do belong to the same installation).

[Conrad Huang]

Can you run that command with the --debug flag? It should produce more information about what pip is doing during installation.

[Tristan Croll]

OK - stdout (make_win.log) and stderr (make_win_debug.log) from running 
with --debug attached.

On 2019-11-27 00:19, ChimeraX wrote:

make_win.log​

make_win_debug.log​

[Tristan Croll]

Added by email2trac

[Tristan Croll]

Added by email2trac

[Conrad Huang]

That's very odd. As a guess, it might have to do with differences in start up or default locations between ChimeraX.exe and python.exe. Can you try using the command:

"c:\Program Files\ChimeraX-daily\ChimeraX\bin\ChimeraX.exe" --nogui --cmd "devel clean .; devel install .; exit

and see if it behaves better?

[Tristan Croll]

That doesn’t work - at least not in the standard Windows command shell. ChimeraX.exe —nogui just returns immediately without doing anything. I filed a ticket on that (probably 2 years ago by now). I can try running the command from *within* the ChimeraX gui to see what happens.

What’s really odd is that it doesn’t seem to do the same thing with ISOLDE.
 

 

[Greg Couch]

ChimeraX-console --nogui should give some output. Does this still happen?

[Elaine Meng]

changed to non-feedback because that was the only way to change owner; change back if needed