-
Notifications
You must be signed in to change notification settings - Fork 557
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
PGCLI takes a long time to start #1041
Comments
@j-bennet I ran
@nhumrich can you reproduce the problem on other machines? |
@zzl0 I don't have other machines to test on, want to provide one for me ;) I assume running in a fresh virtual environment or host wont have the same effect, because this isn't happening for everyone. My guess is its probably due to a weird setup where I have kwallet installed, but I don't use KDE. |
@nhumrich I don't know the root cause of For |
yes, just running |
@zzl0 I think this would be the best thing we can do on |
@nhumrich Our fix got merged, pgcli (master branch) should work properly if you disable keyring in your config. |
Closed via #1046. |
works now. Thank you. |
Description
Anytime I run pgcli, it takes forever to do anything. It almost seems like it hangs, but if I wait long enough, it eventually works. I initially suspected it was doing something with the keyring because the first time I left it running for a while, the kwallet menu came up. I tried to disable the keyring in the config file and it still takes a long time to load. It even takes a while when connecting to a local database. Everything connects instantly using psql.
Even just running
pgcli --version
takes forever to load. It somehow looks like its still trying to do something with the keyring, if I ctrl+c in the middle of hanging I get a stack trace that looks like this:Your environment
Arch linux, pip installed pgcli.
pip freeze shows:
PGCLI has version: Version: 2.1.0
arch linux: 5.0.2 kernal
Its also worth noting that for some reason its trying to use kwallet even though I don't use kde. I use i3, with no DM
The text was updated successfully, but these errors were encountered: