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
clone issue in 4.0.0 #2178
Comments
CC @kalefranz |
Thanks for posting this issue. The conda 4.0 release was a big deal, and brought many changes with it. Even though we have done more the usual testing, and two public beta releases, we missed this issue. We will probably release conda 4.0.1 on Monday or Tuesday. |
Looks like it is the same issue as #2160, which was closed because it seemed like updating conda fixed it. But it looks like there are some circumstances where it is still an issue. @ilanschnell, I think the problem is that |
This stack trace has been fixed in |
thanks! |
Fix in preparation. |
Fix here: #2193 |
Thanks! When will this be released? |
4.0.2 I assume, do not know the timeline |
Should be fixed with today's |
Hi there, thank you for your contribution to Conda! This issue has been automatically locked since it has not had recent activity after it was closed. Please open a new issue if needed. |
getting this error with
conda==4.0.0
.conda==3.19.3
works just fine.The text was updated successfully, but these errors were encountered: