You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
If a package fails to install it remains listed in the mojoproject.toml file. For example, when I tried to install mojmelo and it failed because I was on the most recent nightly version, it was still listed in the mojoproject.toml file under [dependencies] as mojmelo = “”. When I have the mojoproject.toml file open in VS Code while I'm adding the dependency and it succeeds, the “” is updated to the required version range, in the case of mojmelo “>=24.5.0,<25.0a0”.
This issue isn´t limited to just community packages; this is true in general and created a problem for me a few days ago. When I tried to install a Python package unsuccessfully and then moved on to installing other packages, the package that had failed was blocking my other packages from installing. All I had to do was delete it from the mojoproject.toml file, and everything was good-to-go from there.
Steps to reproduce
magic add
Version Info
- magic 0.5.0 - (based on pixi 0.37.0)
- magic 0.6.0 - (based on pixi 0.39.2)
- Linux-64
- Fedora 40
- x86-64 (AMD)
- [project]
authors = ["David Meaux <email@domain.com>"]
channels = ["conda-forge", "https://conda.modular.com/max-nightly"]
description = "Add a short description here"
name = "magic-test"
platforms = ["linux-64"]
version = "0.1.0"
[tasks]
[dependencies]
max = ">=25.1.0.dev2024121705,<26"
mojmelo = "*"
The text was updated successfully, but these errors were encountered:
Issue description
If a package fails to install it remains listed in the mojoproject.toml file. For example, when I tried to install mojmelo and it failed because I was on the most recent nightly version, it was still listed in the mojoproject.toml file under [dependencies] as mojmelo = “”. When I have the mojoproject.toml file open in VS Code while I'm adding the dependency and it succeeds, the “” is updated to the required version range, in the case of mojmelo “>=24.5.0,<25.0a0”.
This issue isn´t limited to just community packages; this is true in general and created a problem for me a few days ago. When I tried to install a Python package unsuccessfully and then moved on to installing other packages, the package that had failed was blocking my other packages from installing. All I had to do was delete it from the mojoproject.toml file, and everything was good-to-go from there.
Steps to reproduce
Version Info
The text was updated successfully, but these errors were encountered: