grizzled timber
None of us here are Nest users, so excuse any ignorance on my part about this. A contributor made this package.
It does looks like it's meant to work with Fastify: https://github.com/triggerdotdev/trigger.dev/blob/7b3ffe040b710379b8133c86a731f30027f193a7/packages/nestjs/src/index.ts#L201
I'm not sure what version Nest was on at this time. It's a moving target with these things unfortunately.
grizzled timber
Hey, there's a fix for this issue
This branch was merged and I created a special release of the packages for you.
Run this:
npx @trigger.dev/cli@latest update -t 0.0.0-nestfix-20240322145612
It'll switch all the package versions for you.
grizzled timber
Ah sorry my bad, wrong flag.
npx @trigger.dev/cli@latest update --to 0.0.0-nestfix-20240322145612
You might just be better off using v3 though. That doesn't care about frameworks. What are you jobs doing? If we support what you need to do I can give you access
grizzled timber
Creating a socket connection that persists indefinitely until a condition is true isn't a use case we've considered (until now). It definitely won't work with v2 but we think it should work with v3.
The best thing would be to do a simple test and use the CLI deploy command early on and see what happens. We're going to have soft concurrency limits for v3, which means you'll start with a limit and when your account is clearly not doing bad things (like spamming people) the limit can get lifted by requesting more.
What email did you use to sign up for v3 early access? I'll bump you up the list.