You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I get this error because there is something wrong with how I have keyring setup right now (I'm guessing):
g-dbus-error-quark: The name org.freedesktop.secrets was not provided by any .service files (2)
I'll look into what's causing that later. But I thought it would be nice if poetry didn't fail in that case. I don't need it to be using keyring for anything I'm going and was surprised it event supported that.
I applied this patch to get it working again (which was easier for me than diving into what might be wrong with my keyring at the moment).
diff --git a/src/poetry/utils/password_manager.py b/src/poetry/utils/password_manager.py
index e687711b..b5619fe5 100644
--- a/src/poetry/utils/password_manager.py+++ b/src/poetry/utils/password_manager.py@@ -48,7 +48,10 @@ class PoetryKeyring:
import keyring
for name in names:
- credential = keyring.get_credential(name, username)+ try:+ credential = keyring.get_credential(name, username)+ except (RuntimeError, keyring.errors.KeyringError):+ credential = None
if credential:
return HTTPAuthCredential(
username=credential.username, password=credential.password
Not sure if the population of people who have their keyring mis-configured (or something) is large enough to warrant a patch, or if this patch has any bad side-effects. But I thought I would raise an issue just in case.
The text was updated successfully, but these errors were encountered:
Duplicate #1917 -- a PR would be welcome, though there are more spots in the code that may need better error handling. A log message is also important here as well, I think.
-vvv
option).Issue
-vvv output
I get this error because there is something wrong with how I have keyring setup right now (I'm guessing):
I'll look into what's causing that later. But I thought it would be nice if poetry didn't fail in that case. I don't need it to be using keyring for anything I'm going and was surprised it event supported that.
I applied this patch to get it working again (which was easier for me than diving into what might be wrong with my keyring at the moment).
Not sure if the population of people who have their keyring mis-configured (or something) is large enough to warrant a patch, or if this patch has any bad side-effects. But I thought I would raise an issue just in case.
The text was updated successfully, but these errors were encountered: