-
Notifications
You must be signed in to change notification settings - Fork 19
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
Stacktrace Shown rather than standard error message when libmamba gets HTTP 404 #68
Comments
We could move all downloads back into Python, now that it is multithreaded. |
@jaimergp Have we fixed this in the recent commits in conda-libmamba-solver? |
Nop, this is part of the vendored |
That said, we could try @dholth's suggestion. We are already doing it for S3/FTP channels. Maybe with an option at first? |
We will need to move the repodata.json downloads back into Python for incremental repodata. The merged parallel package downloads feature should already provide great package download speed. |
Ok, I can start working on this but I'd like to see the plugin work finished first so there's no more rebase issues. |
This will probably fixed by #65 |
(I've moved this issue from the conda repo here) |
This comment was marked as off-topic.
This comment was marked as off-topic.
Different problem, but thanks for the report! See #140 @AlbertDeFusco |
Checklist
What happened?
When you try to use a non-existent channel in conda with the default solver you get a helpful HTTP 404 error.
But when you use libmamba:
Conda Details
conda info
conda config
conda list
Error Report
The text was updated successfully, but these errors were encountered: