Zachary Liu

I also ran into this issue on Vercel with a patch that touched multiple source files. If you just need to patch two files, a hacky workaround is to split...

Looks like this is actively being worked on (https://github.com/prisma/client-planning/issues/21, https://github.com/prisma/prisma/issues/9601) and in fact much of the implementation is already complete too (https://github.com/prisma/prisma/pull/10764).

We got context propagation working on top of Prisma's tracing feature by writing a custom `ContextManager` to expose the active Datadog span context to OpenTelemetry. You still need to initialize...

As a workaround for Next.js, setting the `release` explicitly using Vercel's built-in `NEXT_PUBLIC_VERCEL_GIT_COMMIT_SHA` var seems to work: ```ts Sentry.init({ // ... release: process.env.NEXT_PUBLIC_VERCEL_GIT_COMMIT_SHA, }); ```

I was able to work around this issue by reloading the tile cache after calling `addImage` with the real data, although this does involve a bunch of hidden APIs. ```ts...

Yep, I got it working locally with a patch, so I'll try to clean it up for a PR. @orta Do you happen to know which TypeScript APIs are best...

The lint rule doesn't run on internal library code, but it does look at the _exported_ library types, since it can be used to help detect invalid library usage. These...

Sure! I'll push an update later to make those changes.

This issue seems to be specific to this extension needing to reconstruct a method call to the replica: https://github.com/prisma/extension-read-replicas/blob/3c1a7127b4c80a3352893d8bea71c73898d8d391/src/extension.ts#L72-L76 The fluent API gets translated into `operation: 'findFirst', args: { select:...