Closed samtygier-stfc closed 1 year ago
I can reproduce locally if I install with mamba env create -f https://raw.githubusercontent.com/mantidproject/mantidimaging/main/environment.yml
. And run python -m mantidimaging
from that environment. I can fix by switching numexpr from 2.8.1p y39ha90e767_1 intel
to 2.8.3 mkl_py39h6189487_1 conda-forge/linux-64
So a quick work around is mamba activate mantidimaging-nightly && mamba install numexpr=2.8.3
python setup.py create_dev_env
installs the 2.8.3 version from conda-forge. This uses the mamba env create
underneath, the difference is that it explicitly puts numexpr=2.8.*
in the environment file rather than getting it from the mantidimaging package dependencies.
Options:
conda-forge::numexpr
as a specifier. For us numexpr is specified in meta.yaml
, which accepts this, but it is not propagated into the package metadata, so at the user install step they would still get the bad package.
channel_priority: strict
conda setting. There does not seem to be a way for use to put this in the env file or on the command line. This would work, but means asking users to set a non-default configuration, so endless troubleshooting.IDAaaS has updated and is working now.
Summary
Crash on starting Mantid Imaging on IDAaaS
Steps To Reproduce
Launch Mantid Imaging Unstable on IDAaaS
Expected Behaviour
Current Behaviour
Crash, see below
Context
Mantid Imaging 2.5.0a4.post8
Failure Logs
Screenshot(s)