Fix linting workflows #1836
Merged
Fix linting workflows #1836
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
to fix an issue where workflows failed
ThomasHepworth
approved these changes
Jan 12, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The
autoblackandlintingworkflows have recently stopped working (see e.g. this job run) with error/home/runner/.local/venv/bin/python: error while loading shared libraries: libpython3.9.so.1.0: cannot open shared object file: No such file or directory, which is some sort of virtual env error.I don't know what change triggered this error (as neither poetry nor the install-poetry action have had any new releases), but it seems going from latest poetry (1.7.1), the default, to 1.7.0 fixes things, so have pinned that version for all workflows without a version pinned.