Closed sanderland closed 2 years ago
Also ran into this in the following GitHub Action: https://github.com/catalystneuro/neuroconv/runs/8136194375?check_suite_focus=true
Can confirm pinning requirement to keyring<=23.8.2
works as a temporary fix.
We also ran into this issue with pipelines in GCP Cloud Build.
ImportError: cannot import name 'properties' from 'keyring.util'
this should be fixed with the newest release of keyrings.google-artifactregistry-auth. Please let me know if the issue persists, thanks!
I just want to note that this issue is not specific to keyrings.google-artifactregistry-auth. As I reported above for me it happens due to that import being used also across many keyrings.alt:
(git)lena:~/proj/misc/keyrings.alt[main]git
$> git pull --ff-only
Already up to date.
$> git describe
v4.1.1-6-g010fe59
$> git grep 'from keyring.util import properties'
keyrings/alt/Gnome.py:from keyring.util import properties
keyrings/alt/Google.py:from keyring.util import properties
keyrings/alt/Windows.py:from keyring.util import properties
keyrings/alt/file.py:from keyring.util import properties
keyrings/alt/multi.py:from keyring.util import properties
that is why IMHO should be fixed in keyring itself, and have proper deprecation cycle if desired to change interface and not have properties
available from keyring.util
. I also recommended establishing downstream testing (#594) to prevent such breakages in the future.
Describe the bug
Our pipeline started failing around now. The key issue seemed to have been an unnecessary installation of the latest keyring somewhere in the pipeline.
For keyring-23.9.0, our pipeline failed with
And indeed it seems this file was removed.
Keeping at the older 23.8.2 version works, but it is surprising that a minor version bump would cause it to break.