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

bug with v2.0? #58

Closed
mikemhenry opened this issue Sep 25, 2024 · 7 comments
Closed

bug with v2.0? #58

mikemhenry opened this issue Sep 25, 2024 · 7 comments

Comments

@mikemhenry
Copy link

This used to work in my CI, but with the 2.0 release it breaks now:

/home/runner/.local/bin/micromamba create -y -r /home/runner/micromamba -f environment.yml -n openfe_env python=3.10 pydantic=>1 --log-level warning --rc-file /home/runner/work/_temp/setup-micromamba/.condarc
  critical libmamba Error parsing version ">1". Version contains invalid characters in >1.

Not sure if this is a bug or if I was abusing micromamba syntax. When I pinned the version back to 1.5.6-0 it worked again.

Link to failed CI job: https://github.com/OpenFreeEnergy/openfe/actions/runs/11041820242/job/30672921965

@pavelzw
Copy link
Member

pavelzw commented Sep 26, 2024

You should probably open an issue in the main mamba repo instead

@jjerphan
Copy link
Member

Thank you for opening this issue.

The problem you are observing has been fixed in a release candidate of 2.0.

I cannot reproduce the issue with micromamba 2.0 from conda-forge or from setup-micromamba.

The problem is likely due to an integration issue between setup-micromamba and micromamba-releases which picks a previous release candidate instead of 2.0.0.

We are inspecting this issue.

@jjerphan
Copy link
Member

For now, explicitly setting the version of micromamba (fetched from micromamba-release) that setup-micromamba uses fixes the problem.

This can be done with:

      - name: Setup micromamba
        uses: mamba-org/setup-micromamba@v1.9.0
        with:
          micromamba-version: '2.0.0-0'

@breakbotz
Copy link

breakbotz commented Sep 26, 2024

I believe I'm running into the same (or similar) parsing issue when creating a micromamba environment via CLI (using latest version of micromamba):

micromamba env create --yes --file environment.yml results in:

    The following packages are incompatible
    ├─ aiohttp ~= does not exist (perhaps a typo or a missing channel);
    ├─ anthropic ~= does not exist (perhaps a typo or a missing channel);
    ├─ fluxus ~= does not exist (perhaps a typo or a missing channel);
    ├─ gamma-pytools ~= does not exist (perhaps a typo or a missing channel);
    ├─ google-generativeai ~= does not exist (perhaps a typo or a missing channel);
    ├─ graphviz ~= does not exist (perhaps a typo or a missing channel);
    ├─ groq ~= does not exist (perhaps a typo or a missing channel);
    ├─ ipywidgets ~= does not exist (perhaps a typo or a missing channel);
    ├─ jupyterlab ~= does not exist (perhaps a typo or a missing channel);
... list continues for basically every dependency listed in my environment.yaml which has not changed in months

@jjerphan
Copy link
Member

Hi @breakbotz,

Can you open an issue on mamba-org/mamba so that we can reproduce and fix the error? Thank you.

@breakbotz
Copy link

Hi @breakbotz,

Can you open an issue on mamba-org/mamba so that we can reproduce and fix the error? Thank you.

Created mamba-org/mamba#3472

@SylvainCorlay
Copy link
Member

Closing as it was not related to mamba but to GitHub action picking up a pre-release rather than 2.0.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

5 participants