Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Unnecessary conversion to lowercase leads to error in filepaths #3706

Open
3 tasks done
aryankeluskar opened this issue Dec 21, 2024 · 1 comment
Open
3 tasks done
Assignees
Labels
status::cannot-reproduce The bug could not be reproduced status::user_reply_needed type::bug Something isn't working

Comments

@aryankeluskar
Copy link

aryankeluskar commented Dec 21, 2024

Troubleshooting docs

  • My problem is not solved in the Troubleshooting docs

Anaconda default channels

  • I do NOT use the Anaconda default channels (pkgs/* etc.)

How did you install Mamba?

Mambaforge or latest Miniforge

Search tried in issue tracker

#1324

Latest version of Mamba

  • My problem is not solved with the latest version

Tried in Conda?

I didn't try (cannot try since this is executed on a high-performance computer without access to conda)

Describe your issue

I encountered an issue where mamba automatically converts the specified path to lowercase when searching for an environment YAML file. This behavior causes an error if the actual path contains uppercase letters, as the file cannot be located due to the mismatch in casing.

Steps to Reproduce:

  1. Place the environment YAML file in a directory containing uppercase letters in its path (e.g., /scratch/akeluska/Qiyun-Thesis/structure_guided_pllms/env_gpu.yaml).
  2. Run the following command:
mamba create -p /scratch/akeluska/envs/sgpllms -f "/scratch/akeluska/Qiyun-Thesis/structure_guided_pllms/env_gpu.yaml"
  1. Observe the error message indicating that the file path does not exist.
(prottrans) [akeluska@sg023:/scratch/akeluska/Qiyun-Thesis/structure_guided_pllms]$ mamba create -p /scratch/akeluska/envs/sgpllms -f "/scratch/akeluska/Q
iyun-Thesis/structure_guided_pllms/env_gpu.yaml"

Looking for: ['/scratch/akeluska/qiyun-thesis/structure_guided_pllms/env_gpu.yaml']

error    libmamba Could not open lockfile '/packages/apps/mamba/1.5.8/pkgs/cache/cache.lock'
pkgs/main/linux-64                                          Using cache
error    libmamba Could not open lockfile '/packages/apps/mamba/1.5.8/pkgs/cache/cache.lock'
pkgs/main/noarch                                            Using cache
error    libmamba Could not open lockfile '/packages/apps/mamba/1.5.8/pkgs/cache/cache.lock'
pkgs/r/linux-64                                             Using cache
error    libmamba Could not open lockfile '/packages/apps/mamba/1.5.8/pkgs/cache/cache.lock'
pkgs/r/noarch                                               Using cache
Could not solve for environment specs
The following package could not be installed
└─ /scratch/akeluska/qiyun-thesis/structure_guided_pllms/env_gpu.yaml does not exist (perhaps a typo or a missing channel).

It seems that mamba alters the case of the path during processing, as evidenced by the lowercase path shown in the error message (/scratch/akeluska/qiyun-thesis/...) despite the uppercase letters in the actual path (/scratch/akeluska/Qiyun-Thesis/...).

Expected Behavior:

mamba should preserve the case of the specified file path. I kindly request that the behavior of mamba be reviewed and adjusted to handle case sensitivity of file paths.

mamba info / micromamba info

mamba version : 1.5.8
     active environment : /scratch/akeluska/envs/prottrans
    active env location : /scratch/akeluska/envs/prottrans
            shell level : 1
       user config file : /home/akeluska/.condarc
 populated config files : 
          conda version : 24.5.0
    conda-build version : not installed
         python version : 3.12.2.final.0
                 solver : libmamba (default)
       virtual packages : __archspec=1=zen3
                          __conda=24.5.0=0
                          __cuda=12.5=0
                          __glibc=2.28=0
                          __linux=4.18.0=0
                          __unix=0=0
       base environment : /packages/apps/mamba/1.5.8  (read only)
      conda av data dir : /packages/apps/mamba/1.5.8/etc/conda
  conda av metadata url : None
           channel URLs : https://repo.anaconda.com/pkgs/main/linux-64
                          https://repo.anaconda.com/pkgs/main/noarch
                          https://repo.anaconda.com/pkgs/r/linux-64
                          https://repo.anaconda.com/pkgs/r/noarch
          package cache : /packages/apps/mamba/1.5.8/pkgs
                          /home/akeluska/.conda/pkgs
       envs directories : /packages/envs
                          /home/akeluska/.conda/envs
                          /packages/apps/mamba/1.5.8/envs
               platform : linux-64
             user-agent : conda/24.5.0 requests/2.32.2 CPython/3.12.2 Linux/4.18.0-553.22.1.el8_10.x86_64 rocky/8.10 glibc/2.28 solver/libmamba conda-libmamba-solver/24.1.0 libmambapy/1.5.8
                UID:GID : 2684480:99999875
             netrc file : None
           offline mode : False

Logs

No response

environment.yml

name: sgpllms
channels:
  - pytorch
  - nvidia
  - conda-forge
  - defaults
dependencies:
  - pip
  - python=3.11
  - pytorch
  - pytorch-cuda=11.8
  - pip:
     - -r requirements.in
     - -r requirements-dev.in

~/.condarc

No response

@Hind-M Hind-M added the type::bug Something isn't working label Dec 23, 2024
@Hind-M Hind-M self-assigned this Dec 31, 2024
@Hind-M
Copy link
Member

Hind-M commented Jan 2, 2025

Thank you for reporting this. Unfortunately I couldn't reproduce the issue. Does it work as expected if you use the exact mamba command with the same config and parameters, but with qiyun-thesis for example as the original folder name?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
status::cannot-reproduce The bug could not be reproduced status::user_reply_needed type::bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants