-
Notifications
You must be signed in to change notification settings - Fork 3
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
Unable to run Automous Hegician in Mac, cannot create DB #46
Comments
I can confirm I was getting a problem with the DB as well (not sure if the exact same). Manually removed the Docker images and installed from scratch - this threw some problems when it started doing the tests (file with errors attached), but then starting it again and running live seemed to work OK. However, running tests manually this time, it failed only 1: FAIL: test_does_ah_expire_otm_eth_put_option (main.TestOptionExecutionTester)Traceback (most recent call last): Ran 10 tests in 121.296s FAILED (failures=1) |
Thanks for bringing this to my attention. Definitely some issues with mac builds. @aravintp Can I ask you to check whether you are able to connect to the database externally? @aaugustin4omnis I am 98% sure your issue related to timeouts in the test script. Hit me up on discord so we can have a quick check? |
@8ball030 that's right - it seemed a timeout on connection to the DB. Tried again today, failed with the same error and then I gave some minutes to Docker to finish itself starting up and run all tests again which all completed successfully! Thanks :) |
@aaugustin4omnis Sweet, glad to hear it. I believe that I have resolved this with a new pull request, referenced you in the request |
@8ball030 Thank you for reply! But i'm not sure what database im supposed to connect externally. Am i supposed to have a database running locally? Thank you! |
We are unable to run Automous Hegician in Mac. Error occurs when its creating database.
FATAL: no pg_hba.conf entry for host "172.20.0.1", user "admin", database "cortex", SSL off
Not sure how to move forward.
The text was updated successfully, but these errors were encountered: