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

Raise if conda-meta's pinned is ill-formed #7978

Open
jakirkham opened this issue Nov 19, 2018 · 2 comments
Open

Raise if conda-meta's pinned is ill-formed #7978

jakirkham opened this issue Nov 19, 2018 · 2 comments
Labels
backlog issue has been triaged but has not been earmarked for any upcoming release severity::2 critical; broken functionality with an unacceptably complex workaround source::community catch-all for issues filed by community members stale::recovered [bot] recovered after being marked as stale type::feature request for a new feature or capability

Comments

@jakirkham
Copy link
Member

Currently if someone adds content to conda-meta's pinned file that is ill-formed, it proceeds without raising or in the best case scenario may raise a tangential error message downstream. However this can really start to cause problems. For example, if one accidentally adds quotes around content in pinned that results in this content being blissfully ignored by Conda, causing surprising downstream consequences. Would be nice in these and other cases to validate pinned parses correctly and raise with an informative error if it doesn't. Thus blocking unintentional environment changes (which pinned is intended to avoid) and helping the user to diagnose what went wrong in pinned.

@jezdez jezdez added severity::2 critical; broken functionality with an unacceptably complex workaround source::community catch-all for issues filed by community members tag-environment_spec type::feature request for a new feature or capability labels Sep 17, 2021
@kenodegard kenodegard added plugins::env pertains to conda-env and removed tag::environment-spec labels Jan 18, 2022
@github-actions
Copy link

Hi there, thank you for your contribution!

This issue has been automatically marked as stale because it has not had recent activity. It will be closed automatically if no further activity occurs.

If you would like this issue to remain open please:

  1. Verify that you can still reproduce the issue at hand
  2. Comment that the issue is still reproducible and include:
    - What OS and version you reproduced the issue on
    - What steps you followed to reproduce the issue

NOTE: If this issue was closed prematurely, please leave a comment.

Thanks!

@github-actions github-actions bot added the stale [bot] marked as stale due to inactivity label Jan 19, 2023
@jakirkham
Copy link
Member Author

Let's keep this open

@github-actions github-actions bot added stale::recovered [bot] recovered after being marked as stale and removed stale [bot] marked as stale due to inactivity labels Jan 20, 2023
@beeankha beeankha added backlog issue has been triaged but has not been earmarked for any upcoming release and removed plugins::env pertains to conda-env labels Sep 11, 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 severity::2 critical; broken functionality with an unacceptably complex workaround source::community catch-all for issues filed by community members stale::recovered [bot] recovered after being marked as stale type::feature request for a new feature or capability
Projects
Status: 🆕 New
Development

No branches or pull requests

4 participants