Skip to content
This repository has been archived by the owner on Oct 22, 2021. It is now read-only.

The postgres example does not work out of the box. #24

Open
aniket-patel-ef opened this issue Jul 8, 2020 · 4 comments
Open

The postgres example does not work out of the box. #24

aniket-patel-ef opened this issue Jul 8, 2020 · 4 comments

Comments

@aniket-patel-ef
Copy link

Got this error:
ERRO[0003] Unable to interpolate string '${{ job.services.postgres.ports[5432] }}' - [TypeError: Cannot access member 'ports' of undefined]
[Postgres Service Example/vm-job ] ⭐ Run node client.js
| (node:32) UnhandledPromiseRejectionWarning: Error: connect ECONNREFUSED 127.0.0.1:5432
| at TCPConnectWrap.afterConnect [as oncomplete] (net.js:1137:16)
| (node:32) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag --unhandled-rejections=strict (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 1)
| (node:32) [DEP0018] DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero exit code.
| /github/workspace/postgres/client.js:14
| if (err) throw err
| ^
|
| Error: Connection terminated unexpectedly

@rc-keaton
Copy link

Bumping this - same exact error happened when I tried running it

@Potherca
Copy link

I am not having this issue at all. When I fork this repo and push to main all example pass ✔️

Are you seeing this error on GitHub or locally usingact?

@rc-keaton
Copy link

I am not having this issue at all. When I fork this repo and push to main all example pass

Are you seeing this error on GitHub or locally usingact?

Locally with act. I'm using act version 0.2.17 on Ubuntu 18.04.3

@Potherca
Copy link

Potherca commented Jan 4, 2021

Yeah, I'm seeing it locally too. I guess we should head over to act and see what we can find there.

@aniket-patel-ef Did you encounter this issue locally or on GitHub? If it is locally, I think this issue can be closed.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants