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

rules.c solver_addrule: Assertion !p2 && d > 0 failed #387

Open
2 tasks done
andr0s opened this issue Nov 19, 2023 · 4 comments
Open
2 tasks done

rules.c solver_addrule: Assertion !p2 && d > 0 failed #387

andr0s opened this issue Nov 19, 2023 · 4 comments
Labels
stale [bot] marked as stale due to inactivity type::bug describes erroneous operation, use severity::* to classify the type

Comments

@andr0s
Copy link

andr0s commented Nov 19, 2023

Checklist

  • I added a descriptive title
  • I searched open reports and couldn't find a duplicate

What happened?

a few dozen of packages, dockerfile.

Always crashing with error: rules.c solver_addrule: Assertion !p2 && d > 0 failed.

Conda installed as:

RUN conda install -n base conda-libmamba-solver &&
conda config --set solver libmamba

Conda Info

No response

Conda Config

No response

Conda list

No response

Additional Context

No response

@andr0s andr0s added the type::bug describes erroneous operation, use severity::* to classify the type label Nov 19, 2023
@github-project-automation github-project-automation bot moved this to 🆕 New in 🧭 Planning Nov 19, 2023
@jaimergp
Copy link
Contributor

Hey @andr0s, thanks for the report!

Would you be able to share your Dockerfile contents (redact as necessary). I'm mostly interested in which conda packages you are trying to install using the libmamba solver. If possible, it would also help you have verbose logs attached. You can enable those with the -vvv flag.

With that info I can try get a reproducer and take a deeper look at the issue. Thanks!

@andr0s
Copy link
Author

andr0s commented Nov 20, 2023

@jaimergp I found the problem :) It was because I had one package in the requirements.txt in a form of libname>=1.2.3, i.e. it had the version specified. Because it was a pip requirements file. After I removed the version (and >= obviously), things worked just fine

@jaimergp
Copy link
Contributor

Interesting! That's supposed to work too 😂 You should have obtained a "package not found error" if anything, but definitely not a hard crash. Was it using a weird operator or was it really >=? I don't get it otherwise, but hey, happy you found a solution!

Copy link

Hi there, thank you for your contribution!

This issue has been automatically marked as stale because it has not had recent activity. It will be closed automatically if no further activity occurs.

If you would like this issue to remain open please:

  1. Verify that you can still reproduce the issue at hand
  2. Comment that the issue is still reproducible and include:
    - What OS and version you reproduced the issue on
    - What steps you followed to reproduce the issue

NOTE: If this issue was closed prematurely, please leave a comment.

Thanks!

@github-actions github-actions bot added the stale [bot] marked as stale due to inactivity label Nov 20, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
stale [bot] marked as stale due to inactivity type::bug describes erroneous operation, use severity::* to classify the type
Projects
Status: 🆕 New
Development

No branches or pull requests

2 participants