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

Prevent execution of spurious clean-up step, which then crashes. #14581

Merged
merged 2 commits into from
Feb 16, 2023

Conversation

rburema
Copy link
Member

@rburema rburema commented Feb 16, 2023

The clean-up step for setting up Python and pip assumes that you do at least something with those programs -- and so that cache folders have been made, that need to be cleaned up. If nothing happens, the clean-up step then crashes on the non-existent cache folder.

The clean-up step for setting up Python and pip assumes that you do at least something with those programs -- and so that cache folders have been made, that need to be cleaned up. If nothing happens, the clean-up step then crashes on the non-existant cache folder.
Otherwise those if checks placed in the last commit won't even do anything if there _is_ a change in the printer definitions.
Copy link
Member

@jellespijker jellespijker left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

thanks for picking this up

@jellespijker jellespijker merged commit d20b37b into main Feb 16, 2023
@jellespijker jellespijker deleted the fix_printer_linter branch February 16, 2023 20:58
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants