fix: add debug output to panic message

prisma · May 13, 2020 · da8f05e · da8f05e
1 parent f1eb2d7
commit da8f05e
Show file tree

Hide file tree

Showing 2 changed files with 14 additions and 1 deletion.
diff --git a/src/packages/engine-core/src/NodeEngine.ts b/src/packages/engine-core/src/NodeEngine.ts
@@ -21,6 +21,7 @@ import { convertLog, RustLog, RustError } from './log'
 import { spawn, ChildProcessWithoutNullStreams } from 'child_process'
 import byline from './byline'
 import bent from 'bent'
+import { getLogs } from '@prisma/debug'
 
 const debug = debugLib('engine')
 const exists = promisify(fs.exists)
@@ -564,7 +565,9 @@ ${this.lastErrorLog.fields.message}: ${this.lastErrorLog.fields.reason} in
 ${this.lastErrorLog.fields.file}:${this.lastErrorLog.fields.line}:${
               this.lastErrorLog.fields.column
             }`
-            const url = getGithubIssueUrl({ title: errorDescription })
+            const logs = getLogs()
+            const body = `Hi Prisma Team! My Prisma Client just crashed. These are the logs: \`\`\`\n${logs}\`\`\``
+            const url = getGithubIssueUrl({ title: errorDescription, body })
             console.error(`${errorDescription}
 
 This is a non-recoverable error which probably happens when the Prisma Query Engine has a panic.

diff --git a/src/pnpm-lock.yaml b/src/pnpm-lock.yaml