SNOW-1553756 use forked version 99design/keyring
without kwallet/secretservice to avoid dbus issue
#1296
+4
−14
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.
#1183 for the full story
Description
99designs/keyring
has a long outstanding bug (99designs/keyring#103) which on certain Linux distros, results in runaway dbus-daemon processes. It seems to originate fromkwallet/secretservice
modules of the said library, which we in gosnowflake do not even use; we use a JSON file for temporal credential storage on Linux.Yet, suffering from the issue originating from the bug, because the modules are of course initialized (= bug happens) even when not used.
A long term and nice solution will be entirely replacing
99design/keyring
with a different implementation, but given the priorities so far and the foreseeable near future, it's not realistic to expect it will happen very soon.Thus: workaround; use a fork of
keyring
as many other people to, which simply nukeskwallet
andsecretservice
where the bug is coming from. 👌Checklist