#node 18 support

20 messages · Page 1 of 1 (latest)

cursive acorn
#

One of my actions stopped working, and I'm having a hard time debugging.

I see this:

logging.ts:28 [CONVEX A(actions/getComputer)] Invalid state: chunk ArrayBuffer is zero-length or detached

On this deployment: dusty-caterpillar-550

Any thoughts?
Thanks,
-s

cursive acorn
#

What node version do the actions run in?

hollow sluice
#

Actions run in Node.js 16

hollow sluice
#

@cursive acorn does this happen consistently? it sounds a bit like the sort of thing that would happen in an unresolved promise, then when the runtime environment wakes back up to service the next request would still be there, but would fail because resources are no longer available

#

that doesn't sound very helpful when I read what I wrote

#

Is it possible you're not awaiting some promises?

cursive acorn
#

It's consistently failing

#

it was working yesterday 😕

#

It works locally on my node 18 installation

#

but when I start using node-fetch it fails locally

#

so I'm making some headway

#

but i have no idea why it worked yesterday

#

and not today

cursive acorn
#

Is it possible to use node 18?

cursive acorn
#

well, it took a long time... but I finally polyfilled enough things to make it work for today

slim oyster
#

I will explore whether we can do node18

cursive acorn
#

Thanks! In the meantime, I'm putting forward a proposal for a moratorium on all node development for 6 months, while we all stop to think about what we're doing.

dreamy jasper
#

node 18 support

alpine minnow
#

We are running actions in Node18 now. Since node16 is getting end of life in five months, we don't allow you to opt-in to older version. We will likely provide you ability to specify a version in the future.

cursive acorn
#

My actions aren't seeing fetch natively, is there a way to upgrade my instance to node18?