We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
pixi lock
I have checked that this issue has not already been reported.
I have confirmed this bug exists on the latest version of pixi, using pixi --version.
pixi --version
https://github.com/trim21/pixi-bug-3283
When I have pixi.toml without valid resolution, pixi will stop resolve without showing any useful information unless I use --no-progress
--no-progress
I reproduce this in powershell, but looks like it doesn't only happened in powershell
https://discord.com/channels/1082332781146800168/1082338253925003385/1348747360464797786
❯❯ ~/proj/pixi (renovate/conda -1) pixi --version pixi 0.42.0 ❯❯ ~/proj/pixi (renovate/conda -1) pixi update ⠒ default:win-64 [00:00:00] loading repodata ⠒ default:osx-64 [00:00:00] loading repodata ⠒ default:osx-arm64 [00:00:00] resolving conda ⠒ default:linux-aarch6400:00:00] loading repodata ⠒ default:linux-64 [00:00:00] loading repodata ⠒ default:osx-64 [00:00:00] loading repodata ⠒ default:linux-aarch6400:00:00] loading repodata ⠒ default:linux-64 [00:00:00] loading repodata ⠒ pypi-gen:osx-64 [00:00:00] loading repodata ⠒ pypi-gen:linux-aarch6400:00:00] loading repodata ⠒ trampoline:linux-aarch64 [00:00:00] loading repodata ⠒ trampoline:osx-64 [00:00:00] loading repodata ⠒ trampoline:linux-64 [00:00:00] loading repodata ❯❯ ~/proj/pixi (renovate/conda -1) pixi lock ⠒ pypi-gen:win-64 [00:00:00] loading repodata ⠒ pypi-gen:linux-64 [00:00:00] loading repodata ⠒ default:win-64 [00:00:00] loading repodata ⠒ pypi-gen:linux-aarch6400:00:00] loading repodata ⠒ pypi-gen:osx-64 [00:00:00] loading repodata ⠒ pypi-gen:linux-64 [00:00:00] loading repodata ⠒ pypi-gen:linux-aarch6400:00:00] loading repodata ⠒ pypi-gen:osx-64 [00:00:00] loading repodata ⠒ default:osx-arm64 [00:00:00] resolving conda ⠒ default:linux-aarch6400:00:00] loading repodata ⠒ default:osx-64 [00:00:00] loading repodata ⠒ trampoline:win-64 [00:00:00] loading repodata ⠒ trampoline:linux-aarch64 [00:00:00] loading repodata ⠒ trampoline:osx-64 [00:00:00] loading repodata test-export:osx-64 .. ❯❯ ~/proj/pixi (renovate/conda -1) pixi lock --quiet ⠚ default:win-64 [00:00:00] loading repodata ⠚ default:linux-aarch6400:00:00] loading repodata ⠚ default:osx-64 [00:00:00] loading repodata ⠚ default:linux-64 [00:00:00] loading repodata ⠚ default:osx-arm64 [00:00:00] loading repodata ⠚ default:win-64 [00:00:00] loading repodata ⠚ default:linux-aarch6400:00:00] loading repodata ⠚ default:osx-64 [00:00:00] loading repodata ⠚ default:osx-arm64 [00:00:00] loading repodata ⠚ pypi-gen:win-64 [00:00:00] loading repodata ⠚ pypi-gen:linux-64 [00:00:00] loading repodata ❯❯ ~/proj/pixi (renovate/conda -1) pixi lock --no-progress --color=never --quiet Error: × failed to solve the conda requirements of 'test-export' 'osx-arm64' ╰─▶ Cannot solve the request because of: No candidates were found for micromamba >=2.0.6.
it should show error message at last
The text was updated successfully, but these errors were encountered:
Thanks for letting us know!
We can reproduce it with any of the solving commands.
Sorry, something went wrong.
baszalmstra
Successfully merging a pull request may close this issue.
Checks
I have checked that this issue has not already been reported.
I have confirmed this bug exists on the latest version of pixi, using
pixi --version
.Reproducible example
https://github.com/trim21/pixi-bug-3283
Issue description
When I have pixi.toml without valid resolution, pixi will stop resolve without showing any useful information unless I use
--no-progress
I reproduce this in powershell, but looks like it doesn't only happened in powershell
https://discord.com/channels/1082332781146800168/1082338253925003385/1348747360464797786
Expected behavior
it should show error message at last
The text was updated successfully, but these errors were encountered: