Repository navigation
fix(server-utils): Require a parent span for Prisma operations - #25863
nicohrubec wants to merge 3 commits into
Conversation
Co-Authored-By: GPT-6 <codex@openai.com>
size-limit report 📦Compared: c78ca1f (PR test merge using develop at 61d2b26) Against: 61d2b26 (develop) · base run #64083 ✅ Baseline matches: this diff contains only this PR's changes.
|
Optional E2E testsSome optional checks were not successful. They do not block the merge. 1 not successful, 64 successful. See the run.
Successful checks
|
There was a problem hiding this comment.
Cursor Bugbot has reviewed your changes and found 1 potential issue.
❌ Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, enable autofix in the Cursor dashboard.
Want reviews to match your repository better? Bugbot Learning can learn team-specific rules from PR activity. A team admin can enable Learning in the Cursor dashboard.
Reviewed by Cursor Bugbot for commit 71a98da. Configure here.
Co-Authored-By: GPT-6 <codex@openai.com>
Co-Authored-By: GPT-6 <codex@openai.com>
|
superseded by #25879 |

Why: Prisma creates root DB spans without the application context needed to identify their origin. Require a parent for client spans and v6/v7 engine batches, aligning with the v8 path and other DB integrations.
How to review: Callbacks still execute without a parent; v5 delayed replay keeps resolving recorded parents. Existing Prisma v5/v6 integration suites cover queries with and without an active parent. Focused helper tests cover unparented engine dispatch and parented engine/DB relationships.
Closes #25802