[backport] NFT tracing fixes #84155 and #85323#88124
Conversation
|
Allow CI Workflow Run
Note: this should only be enabled once the PR is ready to go and can only be enabled by a maintainer |
CodSpeed Performance ReportMerging this PR will degrade performance by 20.02%Comparing Summary
Performance Changes
Footnotes
|
4622122 to
aaa5ac9
Compare
07745be to
417eb2a
Compare
Failing test suitesCommit: 417eb2a | About building and testing Next.js
Expand output● app-dir-runtime-config-experimental-edge › transforms correctly using "app-dir-runtime-config-experimental-edge/basic" data
Expand output● built-in-next-font › transforms correctly using "built-in-next-font/page" data |
Tests are missing
Previously, `readFileSync("./data/foo.txt")` was relative to the current file, not relative to `process.cwd()`
The `.contains("/node_modules/")` condition didn't work for npm, where the path might be `"node_modules/.prisma/client"`
This fixes cases of the following error with Prisma and npm
```
Prisma Client could not locate the Query Engine for runtime "rhel-openssl-3.0.x".
We detected that you are using Next.js, learn how to fix this: https://pris.ly/d/engine-not-found-nextjs.
This is likely caused by tooling that has not copied "libquery_engine-rhel-openssl-3.0.x.so.node" to the deployment folder.
Ensure that you ran `prisma generate` and that "libquery_engine-rhel-openssl-3.0.x.so.node" has been copied to "node_modules/.prisma/client".
We would appreciate if you could take the time to share some information with us.
Please help us by answering a few questions: https://pris.ly/engine-not-found-tooling-investigation
The following locations have been searched:
/var/task/node_modules/.prisma/client
/var/task/node_modules/@prisma/client
/vercel/path0/node_modules/@prisma/client
/tmp/prisma-engines
```
417eb2a to
61fbff8
Compare
Backport #84155 and #85323
Doing this in a single PR because the second followup PR touches the exact same lines as the first one, so you can't revert these individually anyway.