bug: unable to intialize: Cannot find matching keyid:

[davidmoshal]

Provide environment information

System:
OS: Linux 6.8 Ubuntu 22.04.5 LTS 22.04.5 LTS (Jammy Jellyfish)
CPU: (32) x64 AMD Ryzen Threadripper 2950X 16-Core Processor
Memory: 41.22 GB / 62.63 GB
Container: Yes
Shell: 5.8.1 - /usr/bin/zsh
Binaries:
Node: 22.10.0 - ~/.nvm/versions/node/v22.10.0/bin/node
Yarn: 1.22.22 - ~/.nvm/versions/node/v22.10.0/bin/yarn
npm: 10.9.0 - ~/.nvm/versions/node/v22.10.0/bin/npm
pnpm: 9.12.2 - ~/.local/share/pnpm/pnpm
bun: 1.1.30 - ~/.bun/bin/bun
Watchman: 4.9.0 - /usr/bin/watchman

Describe the bug

Node 22.10.0
Ubuntu 22

Same error occurs with: pnpm dlx trigger.dev@latest init -p proj_booaykntbgtwgcccoari and
npx trigger.dev@latest init -p proj_booaykntbgtwgcccoari

Trigger.dev (3.3.16)

┌ Initializing project
│
◇ Retrieved your account details for [email protected]
│
◇ Configuring project "au25-scraper" (proj_booaykntbgtwgcccoari)
│
◇ Failed to install @trigger.dev/sdk@latest. Rerun command with --log-level debug for more details.
X Error: Command failed with exit code 1: corepack pnpm add @trigger.dev/sdk@latest
/home/davem/.nvm/versions/node/v22.10.0/lib/node_modules/corepack/dist/lib/corepack.cjs:21535
if (key == null || signature == null) throw new Error(Cannot find matching keyid: ${JSON.stringify({ signatures, keys })});
^

Error: Cannot find matching keyid: {"signatures":[{"sig":"=","keyid":""}],"keys":[{"expires":null,"keyid":"","keytype":"ecdsa-sha2-nistp256","scheme":"ecdsa-sha2-nistp256","key":""}]}
at verifySignature (/home/davem/.nvm/versions/node/v22.10.0/lib/node_modules/corepack/dist/lib/corepack.cjs:21535:47)
at fetchLatestStableVersion (/home/davem/.nvm/versions/node/v22.10.0/lib/node_modules/corepack/dist/lib/corepack.cjs:21553:5)
at process.processTicksAndRejections (node:internal/process/task_queues:105:5)
at async fetchLatestStableVersion2 (/home/davem/.nvm/versions/node/v22.10.0/lib/node_modules/corepack/dist/lib/corepack.cjs:21672:14)
at async Engine.getDefaultVersion (/home/davem/.nvm/versions/node/v22.10.0/lib/node_modules/corepack/dist/lib/corepack.cjs:22292:23)
at async Engine.executePackageManagerRequest (/home/davem/.nvm/versions/node/v22.10.0/lib/node_modules/corepack/dist/lib/corepack.cjs:22390:47)
at async Object.runMain (/home/davem/.nvm/versions/node/v22.10.0/lib/node_modules/corepack/dist/lib/corepack.cjs:23096:5)

Node.js v22.10.0

Reproduction repo

no need this happens in any repo

To reproduce

see above

Additional information

also have this error:

pnpm dlx trigger.dev@latest dev

Trigger.dev (3.3.16)

Key: Version | Task | Run

X Error: The "maxDuration" trigger.config option is now required, and must be at least 5 seconds.

[matt-aitken]

That error about maxDuration means you need to set a value for that in your trigger.config file: https://trigger.dev/docs/runs/max-duration

The corepack issue looks to be an issue with your corepack signatures, and not related to Trigger.dev.

Here are a few steps the user can try to resolve this issue:

1. Update Corepack

Ensure Corepack is up to date, as signature verification issues can often be resolved with newer versions:

corepack prepare pnpm@latest --activate

Then, verify the installed version:

pnpm --version

2. Clear Corepack Cache

Corepack might have cached a corrupted or incomplete binary signature. Clearing the cache may help:

corepack disable
corepack enable

This will force Corepack to re-download the signatures.

[matt-aitken]

Going to close this because I think is a configuration issue, not a bug. But will re-open if that’s not the case.

[davidmoshal]

well actually I'm not the only one to log this issue, it's all very well saying it's a configuration issue, but how is it solved? where is the documentation on this?

[lbnd4249]

I did the below and it worked
npm install -g corepack
corepack cache clean