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

Improve "Prefix record insertion error:" assertion error #12870

Open
2 tasks done
travishathaway opened this issue Jul 12, 2023 · 0 comments
Open
2 tasks done

Improve "Prefix record insertion error:" assertion error #12870

travishathaway opened this issue Jul 12, 2023 · 0 comments
Labels
backlog issue has been triaged but has not been earmarked for any upcoming release source::anaconda created by members of Anaconda, Inc. type::bug describes erroneous operation, use severity::* to classify the type

Comments

@travishathaway
Copy link
Contributor

travishathaway commented Jul 12, 2023

Checklist

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

What happened?

Every once in a while we get users reporting the assertion error raised here:

assert prefix_record.name not in self._prefix_records, (
"Prefix record insertion error: a record with name %s already exists "
"in the prefix. This is a bug in conda. Please report it at "
"https://github.com/conda/conda/issues" % prefix_record.name
)

Here are the following issues that have reported it:

What should happen?

I think the better solution would be to replace this assertion error with an actual conda error. Furthermore, we should also provide some sort of actionable advice. I believe that this error could be overcome by simply removing and recreating the environment. If it's the base environment, we will want to recommend another action (perhaps reverting it to an early state).

No matter what happens, I do not want a message there that instructs users to create new issues in this queue without giving any advice on how they may be able to fix it.

Additional context

I also think that it would be safe to close the issues linked above once we have completed this issue.

@travishathaway travishathaway added type::bug describes erroneous operation, use severity::* to classify the type source::anaconda created by members of Anaconda, Inc. backlog issue has been triaged but has not been earmarked for any upcoming release labels Jul 12, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
backlog issue has been triaged but has not been earmarked for any upcoming release source::anaconda created by members of Anaconda, Inc. type::bug describes erroneous operation, use severity::* to classify the type
Projects
Status: 🆕 New
Development

No branches or pull requests

1 participant