-
Notifications
You must be signed in to change notification settings - Fork 257
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
Error: failed to refresh connections: pq: server "steampipe" does not exist #319
Comments
@darrenlewisexperian Thanks for reporting this and sorry for the inconvenience. I've been able to reproduce, and we're currently investigating for a workaround / fix. |
… where changes are not committed on Linux #319
I believe we've nailed this one down! Beyond the gross-ness of crash on first install (sorry, ugh) ... the root cause is interesting. We do a number of Postgres options when running to optimize performance, memory etc for our embedded foreign data wrapper. (We're pretty much running an in-memory Postgres DB.) One setting, We're running through the test & release process now, so hope to have v0.3.2 fixing this available soon. I'll follow up here once it's published and we've done a final install test. |
@darrenlewisexperian @vielmetti v0.3.2 is now available, and should work if you are doing a clean install. It does in my testing. If you are having trouble from a previous install and still seeing the error above, then please delete your
Please let us know if this works / does not work / etc. Sorry for the hassle and thanks for the help tracking down this tricky timing issue! |
… where changes are not committed on Linux #319
Describe the bug
I've just installled Steampipe but I can't run any queries because it returns an error.
Steampipe version (
steampipe -v
)steampipe version 0.3.0
To reproduce
See above.
Expected behavior
Data should be returned.
Additional context
WSL is disabled on my company machine so I am running the latest Ubuntu docker image from Docker Hub and installing Steampipe on that and running it.
The text was updated successfully, but these errors were encountered: