Failed environment build with mamba

[samuelbray32]

Describe the bug
Building an environment with environment_dlc.yml failed with the error below. Building with the old version was successful.

To Reproduce
In terminal

mamba env create -f environment_dlc.yml

Output

pkgs/main/linux-64 No change
pkgs/main/noarch No change
pkgs/r/linux-64 No change
conda-forge/linux-64 No change
conda-forge/noarch No change
pkgs/r/noarch No change
pytorch/noarch No change
pytorch/linux-64 No change
franklab/noarch No change
edeno/linux-64 No change
edeno/noarch No change
franklab/linux-64 No change

Looking for: ['bottleneck', 'cudatoolkit=11.3', 'ffmpeg', 'ipympl', "jupyterlab[version='>=3.']", 'libgcc', 'matplotlib', 'non_local_detector', "numpy[version='<1.24']", "pip[version='>=20.2.']", 'position_tools', 'pybind11', 'pydotplus', "pyfftw[version='<=0.12.0']", "python[version='>=3.9,<3.10']", "pytorch[version='<1.12.0']", 'ripple_detection', 'seaborn', 'torchaudio', 'torchvision', "track_linearization[version='>=2.3']"]

python: /home/conda/feedstock_root/build_artifacts/libsolv_1671055376962/work/src/rules.c:261: solver_addrule: Assertion `!p2 && d > 0' failed.

[edeno]

Does the current environment.yml build for you as well?

[samuelbray32]

yes, the current environment.yml builds fine

[edeno]

Some potential differences

environment_dlc.yml has:

• numpy<1.24
• panel<=1.3.5

I know the panel restriction was for a specific error with ipython. Not sure where the numpy one comes from.

[samuelbray32]

You were right, it builds without the numpy specification. It seems like the numpy restriction comes from an old commit in the environment.yml

[CBroz1]

I used conda in my testing, thinking it was the less advanced than mamba and more likely to error out than mamba. I hadn't expected mamaba to fail where conda didn't - my bad