I have been spinning wheels on this for a good part of the day. I have HyperDrive (cockroachDB/pg)

I have been spinning wheels on this for a good part of the day. I have HyperDrive (cockroachDB/pg) working with two workers, for whatever reason and I can't figure out what it is, when I run client.connect, it just breaks out of the routine. it doesn't throw an error.

The codes are super duper vanilla:

const client = new Client({ connectionString: env.REWARDS.connectionString });

try{
    await client.connect();
} catch (ex){
    console.log(ex)
}

const client = new Client({ connectionString: env.REWARDS.connectionString });

try{
    await client.connect();
} catch (ex){
    console.log(ex)
}

How do I track this down? It really feels like it has to be config related, but my wrangler files are identical between the three workers.

PPaul Shriner I have been spinning wheels on this for a good part of the day. I have HyperDri...

Matt Silverlock•12/8/23, 11:10 AM

Can you share more details?

what version of node-Postgres? Definitely the same with both?
your binding config?
your hyperdrive config ID?

Mitya•12/8/23, 11:43 AM

Hi all. I'm using Hyperdrive with Postgres via

node-postgres

node-postgres

. I read somewhere that one benefit of Hyperdrive is it handles pooling for you. Does this mean that I can forget about generating/managing pools manually in my JS, and just leave that to Hyperdrive? i.e. I can just use

client.query()

client.query()

rather than

pool.query()

pool.query()

, or am I wrong here?

Paul ShrinerOP•12/8/23, 11:57 AM

Hey Matt!

Here is the binding config.. The weird thing is that all of the workers are hitting the exact same DB and instance.

hyperdrive = [
  { binding="REWARDS", id="40161c14328e4af193ee63631756f6ab" }
]

hyperdrive = [
  { binding="REWARDS", id="40161c14328e4af193ee63631756f6ab" }
]

I have attached screen shots of the Hyperdrive config.

Screen_Shot_2023-12-08_at_6.54.40_AM.png

Screen_Shot_2023-12-08_at_6.56.48_AM.png

Paul ShrinerOP•12/8/23, 11:58 AM

Mitya•12/8/23, 12:11 PM

Why does Wrangler tell me to put the PG connection string (for Hyperdrive use) in my

wrangler.toml

wrangler.toml

, given that this file should be committed? This would mean committing sensitive information. Is there a way instead to have the connection string in

.dev.vars

.dev.vars

kian•12/8/23, 12:15 PM

What is the error message that tells you to do that?

Mitya•12/8/23, 12:17 PM

ERROR: In development, you should use a local postgres connection string to emulate hyperdrive functionality. Please setup postgres locally and set the value of "HYPERDRIVE"'s "localConnectionString" to the postgres connection string in your wrangler.toml

Mitya•12/8/23, 12:18 PM

My dev DB lives on Heroku, so it's a remote DB, not locally-hosted

MMitya My dev DB lives on Heroku, so it's a remote DB, not locally-hosted

Max (@rozenmd)•12/8/23, 2:27 PM

can you file a feature request for that? https://github.com/cloudflare/workers-sdk/issues/new?assignees=&labels=enhancement&projects=&template=feature-request.yaml&title=%F0%9F%9A%80+Feature+Request%3A

MMitya Hi all. I'm using Hyperdrive with Postgres via `node-postgres`. I read somewhere...

Matt Silverlock•12/8/23, 2:28 PM

You don’t need to manage the pool in the client. Further, because Workers are typically short lived, your “pool” wouldn’t last any longer than your Worker invocation. Hyperdrive’s pooling is much, much more robust.

JJames Looks like there's some exciting new developments in the Cloudflare dashboard fo...

Sam•12/8/23, 3:23 PM

Letsgoooo, finally! Thanks team

MMax (@rozenmd)can you file a feature request for that? https://github.com/cloudflare/workers-s...

Mitya•12/8/23, 5:44 PM

Will do.

MMatt Silverlock You don’t need to manage the pool in the client. Further, because Workers are ty...

Mitya•12/8/23, 5:44 PM

Great! Thanks.

MMax (@rozenmd)can you file a feature request for that? https://github.com/cloudflare/workers-s...

Mitya•12/8/23, 5:47 PM

https://github.com/cloudflare/workers-sdk/issues/4578

Mitya•12/8/23, 5:53 PM

Is it possible to load one TOML in local dev and another for live? I'm aware that the TOML files supports environments, but I'm trying to circumvent this issue. Guess not if the file must be named exactly

wrangler.toml

wrangler.toml

Max (@rozenmd)•12/8/23, 6:08 PM

you can pass a path to the config file

Max (@rozenmd)•12/8/23, 6:09 PM

--config
https://developers.cloudflare.com/workers/wrangler/commands/

Commands - Wrangler · Cloudflare Workers docs

Create, develop, and deploy your Cloudflare Workers with Wrangler commands.

Mitya•12/8/23, 6:13 PM

Ah, interesting

Mitya•12/9/23, 12:50 AM

Hi again. My Worker needs to access multiple DBs. Can I set up multiple Hyperdrives under one worker, and how would I model/reference these in the TOML file?

kian•12/9/23, 3:09 AM

Just repeat the [[hyperdrive]] block

Kkian Just repeat the [[hyperdrive]] block

Mitya•12/9/23, 1:48 PM

Right - and then assign a different value to each

binding

binding

param within it, and reference those in my JS to denote which DB to connect to, right?

Mitya•12/9/23, 2:35 PM

When running my worker on CF, for endpoints that talk to Hyperdrive I get an error if I refresh the page soon after getting a response. This seems to happen only for routes that talk to HD, not ones that output a simple, static response. The error is:

A hanging Promise was canceled. This happens when the worker runtime is waiting for a Promise from JavaScript to resolve, but has detected that the Promise cannot possibly ever resolve because all code and events related to the Promise's I/O context have already finished. ✘ [ERROR] Uncaught (in response) Error: The script will never generate a response.

A hanging Promise was canceled. This happens when the worker runtime is waiting for a Promise from JavaScript to resolve, but has detected that the Promise cannot possibly ever resolve because all code and events related to the Promise's I/O context have already finished. ✘ [ERROR] Uncaught (in response) Error: The script will never generate a response.

Any idea what that might be about?

kian•12/9/23, 2:55 PM

Do you have code that reproduces the error?

kian•12/9/23, 2:55 PM

It sounds like you have I/O happening outside of the

fetch

fetch

(or other handlers).

Mitya•12/9/23, 3:15 PM

It seems (thanks to @PurpleBlob ) I was reusuing a DB client. I'm in the process of adapting my app from Express.js use, and hadn't properly changed this part to create a DB client on a per-request basis. So all fixed. Thanks anyway.

jjjrmy•12/10/23, 10:26 PM

I can't wait to try this!

piffie•12/11/23, 9:06 AM

hey guys - is there a clear docu about localconnectionstring? when i run the worker in local mode it tells me i need to add one - does this string has to be fully text, or can i use env variables in it as well? I really dont like to put passwords in the code.

kian•12/11/23, 9:57 AM

It’s just a string.

piffie•12/12/23, 7:32 PM

hmm... so now i have it configured exactly like in the example, but when i launch wrangler dev --remote it tells me Unexpected fields found in top-level field: "hyperdrive"

kian•12/12/23, 7:33 PM

What version is Wrangler?

piffie•12/12/23, 7:37 PM

figured it out - if you never deployed your worker, then its not working. you need to deploy it once to the server, and then the dev --remote works

Rreajim ERROR to create a hyperdrive config: has logined as admin user ``` npx wrangler...

Cyb3r-Jak3•12/13/23, 12:50 PM

You should log out and back in so wrangler can update its permissions as the message says.

kian•12/13/23, 7:29 PM

Do you have a Workers Paid plan?

kian•12/13/23, 7:39 PM

Yeah, you need a paid plan for Hyperdrive.

Sam•12/14/23, 2:02 PM

Is it possible to leave ideas for the Hyperdrive dashboard here? If so, it would be great to add a small (readable) name/description to each Hyperdrive. This will make it more clear for what the Hyperdrive connection is being used. Thanks

Max (@rozenmd)•12/14/23, 2:28 PM

Always feel free to leave feature requests/feedback here MeowHeartCloudflare

Sam•12/14/23, 4:45 PM

What is more recommended while using Hyperdrive?

Opening a connection w/ a query:

Or just simply using Pooling?

kian•12/14/23, 4:47 PM

client

client

is fine

kian•12/14/23, 4:47 PM

Hyperdrive will manage a pool of connections for you.

Sam•12/14/23, 4:48 PM

I'm getting the following without opening a connection: Error: The script will never generate a response.

kian•12/14/23, 4:48 PM

Do you have code to reproduce it?

kian•12/14/23, 4:48 PM

That usually means you're doing stuff in the global scope, which is a no-go in Workers.

Sam•12/14/23, 5:12 PM

I think I know what I'm doing wrong lmao. I'm developing locally, so it's in no way connected through Hyperdrive. So I need to open the connection first

Sam•12/14/23, 6:15 PM

Ok that's not the reason, it's not working in production either. Creating a thread to paste the code. (Sorry for tagging: @kian)