Skip to content
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

[QUESTION] Facing problems with connections - github actions #57

Closed
Leonardo-Rocha opened this issue Jun 6, 2020 · 4 comments
Closed
Labels
question Further information is requested

Comments

@Leonardo-Rocha
Copy link

Hey @halvardssm , I'm using using nessie with local containers and they're working great. However, when I tried to use it in github actions, nessie won't connect (using postgres), it gives me the following error:

PostgresError: password authentication failed for user "root"
    at parseError (https://deno.land/x/postgres@v0.4.1/error.ts:105:10)
    at Connection._readAuthResponse (https://deno.land/x/postgres@v0.4.1/connection.ts:199:13)
    at async Connection.handleAuth (https://deno.land/x/postgres@v0.4.1/connection.ts:188:9)
    at async Connection.startup (https://deno.land/x/postgres@v0.4.1/connection.ts:150:5)
    at async Client.connect (https://deno.land/x/postgres@v0.4.1/client.ts:14:5)
    at async ClientPostgreSQL.prepare (https://deno.land/x/nessie/clients/ClientPostgreSQL.ts:34:5)
    at async run (https://deno.land/x/nessie/cli.ts:71:9)
##[error]Process completed with exit code 1.

Have you already faced this error? Can you help me?
Here are the files:
nessie.config.ts
.env.test
ci.yml

@Leonardo-Rocha Leonardo-Rocha added the question Further information is requested label Jun 6, 2020
@halvardssm
Copy link
Owner

halvardssm commented Jun 6, 2020

Hi @Leonardo-Rocha ! Your hostname should probably be "localhost" in your .env.test. Let me know if this solves it for you 💪

@Leonardo-Rocha
Copy link
Author

It didn't work, same error :(

@halvardssm
Copy link
Owner

hm, try to run it with the -d flag, it should give some debugging output and make it easier for you to see where things are going wrong. Let me know when you have updated with this so that I can take a look 🤔

@halvardssm
Copy link
Owner

I assume this issue has been taken care of, and that this is no longer a problem so I will close this issue 😄

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
question Further information is requested
Projects
None yet
Development

No branches or pull requests

2 participants