graphql-engine icon indicating copy to clipboard operation
graphql-engine copied to clipboard

Neon pulled connection string problem on watch mode

Open tadeumaia opened this issue 1 year ago • 0 comments

Component

CLI -> c/v3-cli Postgres (for issues that clearly relates to Postgres SQL execution) -> c/v3-ndc-postgres

What is the current behaviour?

  1. starting a new project
  2. adding hasura3 metadata add-hub-connector pg_db --dir . --subgraph default --id hasura/postgres --url "postgresql://user:pwd@uri/hs?sslmode=require"
  3. connector added and schema file created
  4. running hasura3 watch --dir.
  5. error: 9:00AM ERR unable to refresh data connector connector config for /Users/tadeumaia/code/personal/invictus/apps/hasura/subgraphs/default/dataconnectors/pg_db/pg_db.hml error="error fetching ndc schema: Post \"https://config-proxy.pro.hasura.io/connectors/postgres\": context canceled"

What is the expected behaviour?

  1. starting a new project
  2. adding hasura3 metadata add-hub-connector pg_db --dir . --subgraph default --id hasura/postgres --url "postgresql://user:pwd@uri/hs?sslmode=require"
  3. connector added and schema file created
  4. running hasura3 watch --dir.
  5. no error message on watch

How to reproduce the issue?

  1. Create a free neon postgress database
  2. Get a connection string for pooled connection
  3. Create a table
  4. add that db to a plain hasura project created from scratch

Please provide any traces or logs that could help here.

error="error fetching connector schema: status: 500, message: error returned from database: prepared statement "sqlx_s_1" already exists"

Any possible solutions/workarounds you're aware of?

The engine does work and the connection was made, build created, but it keeps failing on watch mode.

Keywords

neon, pg

tadeumaia avatar Jan 31 '24 12:01 tadeumaia