(node:1255321) [DEP0169] DeprecationWarning: `url.parse()` behavior is not standardized and prone to errors that have security implications. Use the WHATWG URL API instead. CVEs are not issued for `url.parse()` vulnerabilities.
(Use `node --trace-deprecation ...` to show where the warning was created)
(node:1255386) [DEP0169] DeprecationWarning: `url.parse()` behavior is not standardized and prone to errors that have security implications. Use the WHATWG URL API instead. CVEs are not issued for `url.parse()` vulnerabilities.
(Use `node --trace-deprecation ...` to show where the warning was created)
(node:1268262) [DEP0169] DeprecationWarning: `url.parse()` behavior is not standardized and prone to errors that have security implications. Use the WHATWG URL API instead. CVEs are not issued for `url.parse()` vulnerabilities.
(Use `node --trace-deprecation ...` to show where the warning was created)
(node:1270215) [DEP0169] DeprecationWarning: `url.parse()` behavior is not standardized and prone to errors that have security implications. Use the WHATWG URL API instead. CVEs are not issued for `url.parse()` vulnerabilities.
(Use `node --trace-deprecation ...` to show where the warning was created)
[next-auth][error][NO_SECRET] 
https://next-auth.js.org/errors#no_secret Please define a `secret` in production. Error [MissingSecretError]: Please define a `secret` in production.
    at r.assertConfig (.next/server/chunks/_0788xzv._.js:34:11891)
    at _ (.next/server/chunks/_0788xzv._.js:34:17760)
    at async a (.next/server/chunks/_0788xzv._.js:34:125555)
    at async e.length.t (.next/server/chunks/_0788xzv._.js:34:126998)
    at async Z (.next/server/chunks/[root-of-the-server]__0fyz649._.js:1:5259)
    at async J (.next/server/chunks/[root-of-the-server]__0fyz649._.js:1:6337) {
  code: 'NO_SECRET'
}
[next-auth][error][NO_SECRET] 
https://next-auth.js.org/errors#no_secret Please define a `secret` in production. Error [MissingSecretError]: Please define a `secret` in production.
    at r.assertConfig (.next/server/chunks/_0788xzv._.js:34:11891)
    at _ (.next/server/chunks/_0788xzv._.js:34:17760)
    at async a (.next/server/chunks/_0788xzv._.js:34:125555)
    at async e.length.t (.next/server/chunks/_0788xzv._.js:34:126998)
    at async Z (.next/server/chunks/[root-of-the-server]__0fyz649._.js:1:5259)
    at async J (.next/server/chunks/[root-of-the-server]__0fyz649._.js:1:6337) {
  code: 'NO_SECRET'
}
(node:1270421) [DEP0169] DeprecationWarning: `url.parse()` behavior is not standardized and prone to errors that have security implications. Use the WHATWG URL API instead. CVEs are not issued for `url.parse()` vulnerabilities.
(Use `node --trace-deprecation ...` to show where the warning was created)
[next-auth][error][NO_SECRET] 
https://next-auth.js.org/errors#no_secret Please define a `secret` in production. Error [MissingSecretError]: Please define a `secret` in production.
    at r.assertConfig (.next/server/chunks/_0788xzv._.js:34:11891)
    at _ (.next/server/chunks/_0788xzv._.js:34:17760)
    at async a (.next/server/chunks/_0788xzv._.js:34:125555)
    at async e.length.t (.next/server/chunks/_0788xzv._.js:34:126998)
    at async Z (.next/server/chunks/[root-of-the-server]__0fyz649._.js:1:5259)
    at async J (.next/server/chunks/[root-of-the-server]__0fyz649._.js:1:6337) {
  code: 'NO_SECRET'
}
[next-auth][error][NO_SECRET] 
https://next-auth.js.org/errors#no_secret Please define a `secret` in production. Error [MissingSecretError]: Please define a `secret` in production.
    at r.assertConfig (.next/server/chunks/_0788xzv._.js:34:11891)
    at _ (.next/server/chunks/_0788xzv._.js:34:17760)
    at async a (.next/server/chunks/_0788xzv._.js:34:125555)
    at async e.length.t (.next/server/chunks/_0788xzv._.js:34:126998)
    at async Z (.next/server/chunks/[root-of-the-server]__0fyz649._.js:1:5259)
    at async J (.next/server/chunks/[root-of-the-server]__0fyz649._.js:1:6337) {
  code: 'NO_SECRET'
}
[next-auth][error][NO_SECRET] 
https://next-auth.js.org/errors#no_secret Please define a `secret` in production. Error [MissingSecretError]: Please define a `secret` in production.
    at r.assertConfig (.next/server/chunks/_0788xzv._.js:34:11891)
    at _ (.next/server/chunks/_0788xzv._.js:34:17760)
    at async a (.next/server/chunks/_0788xzv._.js:34:125555)
    at async e.length.t (.next/server/chunks/_0788xzv._.js:34:126998)
    at async Z (.next/server/chunks/[root-of-the-server]__0fyz649._.js:1:5259)
    at async J (.next/server/chunks/[root-of-the-server]__0fyz649._.js:1:6337) {
  code: 'NO_SECRET'
}
[next-auth][error][NO_SECRET] 
https://next-auth.js.org/errors#no_secret Please define a `secret` in production. Error [MissingSecretError]: Please define a `secret` in production.
    at c.assertConfig (.next/server/chunks/ssr/_07pp216._.js:34:11891)
    at q (.next/server/chunks/ssr/_07pp216._.js:34:17763)
    at async h (.next/server/chunks/ssr/_07pp216._.js:35:55413)
    at async E (.next/server/chunks/ssr/_07pp216._.js:35:19651)
    at async F (.next/server/chunks/ssr/_07pp216._.js:35:19708)
    at async g (.next/server/chunks/ssr/[root-of-the-server]__1cft4i_._.js:1:14510) {
  code: 'NO_SECRET'
}
⨯ Error: There is a problem with the server configuration. Check the server logs for more information.
    at h (.next/server/chunks/ssr/_07pp216._.js:35:55661)
    at async E (.next/server/chunks/ssr/_07pp216._.js:35:19651)
    at async F (.next/server/chunks/ssr/_07pp216._.js:35:19708)
    at async g (.next/server/chunks/ssr/[root-of-the-server]__1cft4i_._.js:1:14510) {
  digest: '203228224'
}
(node:1271138) [DEP0169] DeprecationWarning: `url.parse()` behavior is not standardized and prone to errors that have security implications. Use the WHATWG URL API instead. CVEs are not issued for `url.parse()` vulnerabilities.
(Use `node --trace-deprecation ...` to show where the warning was created)
(node:1271455) [DEP0169] DeprecationWarning: `url.parse()` behavior is not standardized and prone to errors that have security implications. Use the WHATWG URL API instead. CVEs are not issued for `url.parse()` vulnerabilities.
(Use `node --trace-deprecation ...` to show where the warning was created)
⨯ Error: Failed to load external module @prisma/client-2c3a283f134fdcb6: Error: Cannot find module '@prisma/client-2c3a283f134fdcb6'
Require stack:
- /home/eligence/daily-app.eligence.dev/.next/server/chunks/ssr/[root-of-the-server]__1xpwcym._.js
- /home/eligence/daily-app.eligence.dev/.next/server/chunks/ssr/[turbopack]_runtime.js
- /home/eligence/daily-app.eligence.dev/.next/server/app/_global-error/page.js
- /home/eligence/nodevenv/daily-app.eligence.dev/24/lib/node_modules/next/dist/server/require.js
- /home/eligence/nodevenv/daily-app.eligence.dev/24/lib/node_modules/next/dist/server/next-server.js
- /home/eligence/nodevenv/daily-app.eligence.dev/24/lib/node_modules/next/dist/server/next.js
- /home/eligence/daily-app.eligence.dev/server.js
- /usr/local/lsws/fcgi-bin/lsnode.js
    at Context.externalRequire [as x] (.next/server/chunks/ssr/[turbopack]_runtime.js:572:15)
    at module evaluation (.next/server/chunks/ssr/[root-of-the-server]__1xpwcym._.js:1:45)
    at instantiateModule (.next/server/chunks/ssr/[turbopack]_runtime.js:757:9)
    at getOrInstantiateModuleFromParent (.next/server/chunks/ssr/[turbopack]_runtime.js:781:12)
    at Context.esmImport [as i] (.next/server/chunks/ssr/[turbopack]_runtime.js:352:20)
    at module evaluation (.next/server/chunks/ssr/_19z-fvf._.js:149:6172)
    at instantiateModule (.next/server/chunks/ssr/[turbopack]_runtime.js:757:9)
    at getOrInstantiateModuleFromParent (.next/server/chunks/ssr/[turbopack]_runtime.js:781:12)
    at Context.esmImport [as i] (.next/server/chunks/ssr/[turbopack]_runtime.js:352:20)
    at module evaluation (.next/server/chunks/ssr/_07pp216._.js:35:326)
⨯ Error: Failed to load external module @prisma/client-2c3a283f134fdcb6: Error: Cannot find module '@prisma/client-2c3a283f134fdcb6'
Require stack:
- /home/eligence/daily-app.eligence.dev/.next/server/chunks/ssr/[root-of-the-server]__1xpwcym._.js
- /home/eligence/daily-app.eligence.dev/.next/server/chunks/ssr/[turbopack]_runtime.js
- /home/eligence/daily-app.eligence.dev/.next/server/app/_global-error/page.js
- /home/eligence/nodevenv/daily-app.eligence.dev/24/lib/node_modules/next/dist/server/require.js
- /home/eligence/nodevenv/daily-app.eligence.dev/24/lib/node_modules/next/dist/server/next-server.js
- /home/eligence/nodevenv/daily-app.eligence.dev/24/lib/node_modules/next/dist/server/next.js
- /home/eligence/daily-app.eligence.dev/server.js
- /usr/local/lsws/fcgi-bin/lsnode.js
    at Context.externalRequire [as x] (.next/server/chunks/ssr/[turbopack]_runtime.js:572:15)
    at module evaluation (.next/server/chunks/ssr/[root-of-the-server]__1xpwcym._.js:1:45)
    at instantiateModule (.next/server/chunks/ssr/[turbopack]_runtime.js:757:9)
    at getOrInstantiateModuleFromParent (.next/server/chunks/ssr/[turbopack]_runtime.js:781:12)
    at Context.esmImport [as i] (.next/server/chunks/ssr/[turbopack]_runtime.js:352:20)
    at module evaluation (.next/server/chunks/ssr/_19z-fvf._.js:149:6172)
    at instantiateModule (.next/server/chunks/ssr/[turbopack]_runtime.js:757:9)
    at getOrInstantiateModuleFromParent (.next/server/chunks/ssr/[turbopack]_runtime.js:781:12)
    at Context.esmImport [as i] (.next/server/chunks/ssr/[turbopack]_runtime.js:352:20)
    at module evaluation (.next/server/chunks/ssr/_07pp216._.js:35:326)
⨯ Error: Failed to load external module @prisma/client-2c3a283f134fdcb6: Error: Cannot find module '@prisma/client-2c3a283f134fdcb6'
Require stack:
- /home/eligence/daily-app.eligence.dev/.next/server/chunks/ssr/[root-of-the-server]__1xpwcym._.js
- /home/eligence/daily-app.eligence.dev/.next/server/chunks/ssr/[turbopack]_runtime.js
- /home/eligence/daily-app.eligence.dev/.next/server/app/_global-error/page.js
- /home/eligence/nodevenv/daily-app.eligence.dev/24/lib/node_modules/next/dist/server/require.js
- /home/eligence/nodevenv/daily-app.eligence.dev/24/lib/node_modules/next/dist/server/next-server.js
- /home/eligence/nodevenv/daily-app.eligence.dev/24/lib/node_modules/next/dist/server/next.js
- /home/eligence/daily-app.eligence.dev/server.js
- /usr/local/lsws/fcgi-bin/lsnode.js
    at Context.externalRequire [as x] (.next/server/chunks/ssr/[turbopack]_runtime.js:572:15)
    at module evaluation (.next/server/chunks/ssr/[root-of-the-server]__1xpwcym._.js:1:45)
    at instantiateModule (.next/server/chunks/ssr/[turbopack]_runtime.js:757:9)
    at getOrInstantiateModuleFromParent (.next/server/chunks/ssr/[turbopack]_runtime.js:781:12)
    at Context.esmImport [as i] (.next/server/chunks/ssr/[turbopack]_runtime.js:352:20)
    at module evaluation (.next/server/chunks/ssr/_19z-fvf._.js:149:6172)
    at instantiateModule (.next/server/chunks/ssr/[turbopack]_runtime.js:757:9)
    at getOrInstantiateModuleFromParent (.next/server/chunks/ssr/[turbopack]_runtime.js:781:12)
    at Context.esmImport [as i] (.next/server/chunks/ssr/[turbopack]_runtime.js:352:20)
    at module evaluation (.next/server/chunks/ssr/_07pp216._.js:35:326)
⨯ Error: Failed to load external module @prisma/client-2c3a283f134fdcb6: Error: Cannot find module '@prisma/client-2c3a283f134fdcb6'
Require stack:
- /home/eligence/daily-app.eligence.dev/.next/server/chunks/ssr/[root-of-the-server]__1xpwcym._.js
- /home/eligence/daily-app.eligence.dev/.next/server/chunks/ssr/[turbopack]_runtime.js
- /home/eligence/daily-app.eligence.dev/.next/server/app/_global-error/page.js
- /home/eligence/nodevenv/daily-app.eligence.dev/24/lib/node_modules/next/dist/server/require.js
- /home/eligence/nodevenv/daily-app.eligence.dev/24/lib/node_modules/next/dist/server/next-server.js
- /home/eligence/nodevenv/daily-app.eligence.dev/24/lib/node_modules/next/dist/server/next.js
- /home/eligence/daily-app.eligence.dev/server.js
- /usr/local/lsws/fcgi-bin/lsnode.js
    at Context.externalRequire [as x] (.next/server/chunks/ssr/[turbopack]_runtime.js:572:15)
    at module evaluation (.next/server/chunks/ssr/[root-of-the-server]__1xpwcym._.js:1:45)
    at instantiateModule (.next/server/chunks/ssr/[turbopack]_runtime.js:757:9)
    at getOrInstantiateModuleFromParent (.next/server/chunks/ssr/[turbopack]_runtime.js:781:12)
    at Context.esmImport [as i] (.next/server/chunks/ssr/[turbopack]_runtime.js:352:20)
    at module evaluation (.next/server/chunks/ssr/_19z-fvf._.js:149:6172)
    at instantiateModule (.next/server/chunks/ssr/[turbopack]_runtime.js:757:9)
    at getOrInstantiateModuleFromParent (.next/server/chunks/ssr/[turbopack]_runtime.js:781:12)
    at Context.esmImport [as i] (.next/server/chunks/ssr/[turbopack]_runtime.js:352:20)
    at module evaluation (.next/server/chunks/ssr/_07pp216._.js:35:326)
⨯ Error: Failed to load external module @prisma/client-2c3a283f134fdcb6: Error: Cannot find module '@prisma/client-2c3a283f134fdcb6'
Require stack:
- /home/eligence/daily-app.eligence.dev/.next/server/chunks/ssr/[root-of-the-server]__1xpwcym._.js
- /home/eligence/daily-app.eligence.dev/.next/server/chunks/ssr/[turbopack]_runtime.js
- /home/eligence/daily-app.eligence.dev/.next/server/app/_global-error/page.js
- /home/eligence/nodevenv/daily-app.eligence.dev/24/lib/node_modules/next/dist/server/require.js
- /home/eligence/nodevenv/daily-app.eligence.dev/24/lib/node_modules/next/dist/server/next-server.js
- /home/eligence/nodevenv/daily-app.eligence.dev/24/lib/node_modules/next/dist/server/next.js
- /home/eligence/daily-app.eligence.dev/server.js
- /usr/local/lsws/fcgi-bin/lsnode.js
    at Context.externalRequire [as x] (.next/server/chunks/ssr/[turbopack]_runtime.js:572:15)
    at module evaluation (.next/server/chunks/ssr/[root-of-the-server]__1xpwcym._.js:1:45)
    at instantiateModule (.next/server/chunks/ssr/[turbopack]_runtime.js:757:9)
    at getOrInstantiateModuleFromParent (.next/server/chunks/ssr/[turbopack]_runtime.js:781:12)
    at Context.esmImport [as i] (.next/server/chunks/ssr/[turbopack]_runtime.js:352:20)
    at module evaluation (.next/server/chunks/ssr/_19z-fvf._.js:149:6172)
    at instantiateModule (.next/server/chunks/ssr/[turbopack]_runtime.js:757:9)
    at getOrInstantiateModuleFromParent (.next/server/chunks/ssr/[turbopack]_runtime.js:781:12)
    at Context.esmImport [as i] (.next/server/chunks/ssr/[turbopack]_runtime.js:352:20)
    at module evaluation (.next/server/chunks/ssr/_07pp216._.js:35:326)
⨯ Error: Failed to load external module @prisma/client-2c3a283f134fdcb6: Error: Cannot find module '@prisma/client-2c3a283f134fdcb6'
Require stack:
- /home/eligence/daily-app.eligence.dev/.next/server/chunks/ssr/[root-of-the-server]__1xpwcym._.js
- /home/eligence/daily-app.eligence.dev/.next/server/chunks/ssr/[turbopack]_runtime.js
- /home/eligence/daily-app.eligence.dev/.next/server/app/_global-error/page.js
- /home/eligence/nodevenv/daily-app.eligence.dev/24/lib/node_modules/next/dist/server/require.js
- /home/eligence/nodevenv/daily-app.eligence.dev/24/lib/node_modules/next/dist/server/next-server.js
- /home/eligence/nodevenv/daily-app.eligence.dev/24/lib/node_modules/next/dist/server/next.js
- /home/eligence/daily-app.eligence.dev/server.js
- /usr/local/lsws/fcgi-bin/lsnode.js
    at Context.externalRequire [as x] (.next/server/chunks/ssr/[turbopack]_runtime.js:572:15)
    at module evaluation (.next/server/chunks/ssr/[root-of-the-server]__1xpwcym._.js:1:45)
    at instantiateModule (.next/server/chunks/ssr/[turbopack]_runtime.js:757:9)
    at getOrInstantiateModuleFromParent (.next/server/chunks/ssr/[turbopack]_runtime.js:781:12)
    at Context.esmImport [as i] (.next/server/chunks/ssr/[turbopack]_runtime.js:352:20)
    at module evaluation (.next/server/chunks/ssr/_19z-fvf._.js:149:6172)
    at instantiateModule (.next/server/chunks/ssr/[turbopack]_runtime.js:757:9)
    at getOrInstantiateModuleFromParent (.next/server/chunks/ssr/[turbopack]_runtime.js:781:12)
    at Context.esmImport [as i] (.next/server/chunks/ssr/[turbopack]_runtime.js:352:20)
    at module evaluation (.next/server/chunks/ssr/_07pp216._.js:35:326)
⨯ Error: Failed to load external module @prisma/client-2c3a283f134fdcb6: Error: Cannot find module '@prisma/client-2c3a283f134fdcb6'
Require stack:
- /home/eligence/daily-app.eligence.dev/.next/server/chunks/ssr/[root-of-the-server]__1xpwcym._.js
- /home/eligence/daily-app.eligence.dev/.next/server/chunks/ssr/[turbopack]_runtime.js
- /home/eligence/daily-app.eligence.dev/.next/server/app/_global-error/page.js
- /home/eligence/nodevenv/daily-app.eligence.dev/24/lib/node_modules/next/dist/server/require.js
- /home/eligence/nodevenv/daily-app.eligence.dev/24/lib/node_modules/next/dist/server/next-server.js
- /home/eligence/nodevenv/daily-app.eligence.dev/24/lib/node_modules/next/dist/server/next.js
- /home/eligence/daily-app.eligence.dev/server.js
- /usr/local/lsws/fcgi-bin/lsnode.js
    at Context.externalRequire [as x] (.next/server/chunks/ssr/[turbopack]_runtime.js:572:15)
    at module evaluation (.next/server/chunks/ssr/[root-of-the-server]__1xpwcym._.js:1:45)
    at instantiateModule (.next/server/chunks/ssr/[turbopack]_runtime.js:757:9)
    at getOrInstantiateModuleFromParent (.next/server/chunks/ssr/[turbopack]_runtime.js:781:12)
    at Context.esmImport [as i] (.next/server/chunks/ssr/[turbopack]_runtime.js:352:20)
    at module evaluation (.next/server/chunks/ssr/_19z-fvf._.js:149:6172)
    at instantiateModule (.next/server/chunks/ssr/[turbopack]_runtime.js:757:9)
    at getOrInstantiateModuleFromParent (.next/server/chunks/ssr/[turbopack]_runtime.js:781:12)
    at Context.esmImport [as i] (.next/server/chunks/ssr/[turbopack]_runtime.js:352:20)
    at module evaluation (.next/server/chunks/ssr/_07pp216._.js:35:326)
⨯ Error: Failed to load external module @prisma/client-2c3a283f134fdcb6: Error: Cannot find module '@prisma/client-2c3a283f134fdcb6'
Require stack:
- /home/eligence/daily-app.eligence.dev/.next/server/chunks/ssr/[root-of-the-server]__1xpwcym._.js
- /home/eligence/daily-app.eligence.dev/.next/server/chunks/ssr/[turbopack]_runtime.js
- /home/eligence/daily-app.eligence.dev/.next/server/app/_global-error/page.js
- /home/eligence/nodevenv/daily-app.eligence.dev/24/lib/node_modules/next/dist/server/require.js
- /home/eligence/nodevenv/daily-app.eligence.dev/24/lib/node_modules/next/dist/server/next-server.js
- /home/eligence/nodevenv/daily-app.eligence.dev/24/lib/node_modules/next/dist/server/next.js
- /home/eligence/daily-app.eligence.dev/server.js
- /usr/local/lsws/fcgi-bin/lsnode.js
    at Context.externalRequire [as x] (.next/server/chunks/ssr/[turbopack]_runtime.js:572:15)
    at module evaluation (.next/server/chunks/ssr/[root-of-the-server]__1xpwcym._.js:1:45)
    at instantiateModule (.next/server/chunks/ssr/[turbopack]_runtime.js:757:9)
    at getOrInstantiateModuleFromParent (.next/server/chunks/ssr/[turbopack]_runtime.js:781:12)
    at Context.esmImport [as i] (.next/server/chunks/ssr/[turbopack]_runtime.js:352:20)
    at module evaluation (.next/server/chunks/ssr/_19z-fvf._.js:149:6172)
    at instantiateModule (.next/server/chunks/ssr/[turbopack]_runtime.js:757:9)
    at getOrInstantiateModuleFromParent (.next/server/chunks/ssr/[turbopack]_runtime.js:781:12)
    at Context.esmImport [as i] (.next/server/chunks/ssr/[turbopack]_runtime.js:352:20)
    at module evaluation (.next/server/chunks/ssr/_07pp216._.js:35:326)
(node:1276505) [DEP0169] DeprecationWarning: `url.parse()` behavior is not standardized and prone to errors that have security implications. Use the WHATWG URL API instead. CVEs are not issued for `url.parse()` vulnerabilities.
(Use `node --trace-deprecation ...` to show where the warning was created)

thread 'tokio-runtime-worker' panicked at /root/.cargo/registry/src/index.crates.io-1949cf8c6b5b557f/futures-timer-3.0.2/src/native/delay.rs:112:21:
timer has gone away
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace
⨯ Error [PrismaClientRustPanicError]: 
Invalid `prisma.user.findUnique()` invocation:


PANIC: timer has gone away

This is a non-recoverable error which probably happens when the Prisma Query Engine has a panic.

https://github.com/prisma/prisma/issues/new?body=Hi+Prisma+Team%21+My+Prisma+Client+just+crashed.+This+is+the+report%3A%0A%23%23+Versions%0A%0A%7C+Name++++++++++++%7C+Version++++++++++++%7C%0A%7C-----------------%7C--------------------%7C%0A%7C+Node++++++++++++%7C+v24.18.0+++++++++++%7C+%0A%7C+OS++++++++++++++%7C+debian-openssl-3.0.x%7C%0A%7C+Prisma+Client+++%7C+6.19.3+++++++++++++%7C%0A%7C+Query+Engine++++%7C+c2990dca591cba766e3b7ef5d9e8a84796e47ab7%7C%0A%7C+Database++++++++%7C+mysql++++++++++++++%7C%0A%0A%0A%0A%23%23+Logs%0A%60%60%60%0Aprisma%3AtryLoadEnv+Environment+variables+not+found+at+null%0Aprisma%3AtryLoadEnv+Environment+variables+not+found+at+undefined%0Aprisma%3AtryLoadEnv+No+Environment+variables+loaded%0Aprisma%3Aclient+checkPlatformCaching%3Apostinstall+false%0Aprisma%3Aclient+checkPlatformCaching%3AciName+%0Aprisma%3AtryLoadEnv+Environment+variables+not+found+at+null%0Aprisma%3AtryLoadEnv+Environment+variables+not+found+at+undefined%0Aprisma%3AtryLoadEnv+No+Environment+variables+loaded%0Aprisma%3Aclient+dirname+%2Fhome%2Feligence%2Fnodevenv%2Fdaily-app.eligence.dev%2F24%2Flib%2Fnode_modules%2F.prisma%2Fclient%0Aprisma%3Aclient+relativePath+..%2F..%2F..%2F..%2F..%2F..%2F..%2Fdaily-app.eligence.dev%2Fprisma%0Aprisma%3Aclient+cwd+%2Fhome%2Feligence%2Fdaily-app.eligence.dev%2Fprisma%0Aprisma%3Aclient+clientVersion+6.19.3%0Aprisma%3Aclient%3AlibraryEngine+internalSetup%0Aprisma%3Aget-platform+Don%27t+know+any+platform-specific+paths+for+%22undefined%22+on+x64+%28x86_64%29%0Aprisma%3Aget-platform+Falling+back+to+%22ldconfig%22+and+other+generic+paths%0Aprisma%3Aclient%3AlibraryEngine+sending+request%2C+this.libraryStarted%3A+false%0Aprisma%3Aget-platform+Found+libssl.so+file+using+%22ldconfig%22+or+other+generic+paths%3A+libssl.so.3%0Aprisma%3Aget-platform+The+parsed+libssl+version+is%3A+3.0.x%0Aprisma%3Aget-platform+Distro+is+%22undefined%22.+Falling+back+to+Prisma+engines+built+for+%22debian%22.%0Aprisma%3Aclient%3Aengines%3AresolveEnginePath+enginePath+%2Fhome%2Feligence%2Fnodevenv%2Fdaily-app.eligence.dev%2F24%2Flib%2Fnode_modules%2F.prisma%2Fclient%2Flibquery_engine-debian-openssl-3.0.x.so.node%0Aprisma%3Aclient%3AlibraryEngine+library+starting%0A%60%60%60%0A%0A%23%23+Client+Snippet%0A%60%60%60ts%0A%2F%2F+PLEASE+FILL+YOUR+CODE+SNIPPET+HERE%0A%60%60%60%0A%0A%23%23+Schema%0A%60%60%60prisma%0A%2F%2F+PLEASE+ADD+YOUR+SCHEMA+HERE+IF+POSSIBLE%0A%60%60%60%0A%0A%23%23+Prisma+Engine+Query%0A%60%60%60%0A%0A%60%60%60%0A&title=PANIC%3A+timer+has+gone+away&template=bug_report.yml

If you want the Prisma team to look into it, please open the link above 🙏
To increase the chance of success, please post your schema and a snippet of
how you used Prisma Client in the issue. 

    at async n (.next/server/app/parent/page.js:1:7076)
    at async k (.next/server/app/parent/page.js:2:51013) {
  clientVersion: '6.19.3',
  digest: '129242204'
}
/home/eligence/nodevenv/daily-app.eligence.dev/24/bin/node: fork: retry: Resource temporarily unavailable
/home/eligence/nodevenv/daily-app.eligence.dev/24/bin/node: fork: retry: Resource temporarily unavailable
/home/eligence/nodevenv/daily-app.eligence.dev/24/bin/node: fork: retry: Resource temporarily unavailable
/home/eligence/nodevenv/daily-app.eligence.dev/24/bin/node: fork: retry: Resource temporarily unavailable
/home/eligence/nodevenv/daily-app.eligence.dev/24/bin/node: fork: Resource temporarily unavailable
/home/eligence/nodevenv/daily-app.eligence.dev/24/bin/node: fork: retry: Resource temporarily unavailable
/home/eligence/nodevenv/daily-app.eligence.dev/24/bin/node: fork: retry: Resource temporarily unavailable
/home/eligence/nodevenv/daily-app.eligence.dev/24/bin/node: fork: retry: Resource temporarily unavailable
/home/eligence/nodevenv/daily-app.eligence.dev/24/bin/node: fork: retry: Resource temporarily unavailable
/home/eligence/nodevenv/daily-app.eligence.dev/24/bin/node: fork: Resource temporarily unavailable
/home/eligence/nodevenv/daily-app.eligence.dev/24/bin/node: fork: retry: Resource temporarily unavailable
/home/eligence/nodevenv/daily-app.eligence.dev/24/bin/node: fork: retry: Resource temporarily unavailable
/home/eligence/nodevenv/daily-app.eligence.dev/24/bin/node: fork: retry: Resource temporarily unavailable
(node:1276837) [DEP0169] DeprecationWarning: `url.parse()` behavior is not standardized and prone to errors that have security implications. Use the WHATWG URL API instead. CVEs are not issued for `url.parse()` vulnerabilities.
(Use `node --trace-deprecation ...` to show where the warning was created)

thread '<unnamed>' panicked at /root/.cargo/registry/src/index.crates.io-1949cf8c6b5b557f/tokio-1.45.1/src/runtime/scheduler/multi_thread/worker.rs:460:13:
OS can't spawn worker thread: Resource temporarily unavailable (os error 11)
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace
fatal runtime error: failed to initiate panic, error 5, aborting
(node:1276983) [DEP0169] DeprecationWarning: `url.parse()` behavior is not standardized and prone to errors that have security implications. Use the WHATWG URL API instead. CVEs are not issued for `url.parse()` vulnerabilities.
(Use `node --trace-deprecation ...` to show where the warning was created)

thread '<unnamed>' panicked at /root/.cargo/registry/src/index.crates.io-1949cf8c6b5b557f/tokio-1.45.1/src/runtime/scheduler/multi_thread/worker.rs:460:13:
OS can't spawn worker thread: Resource temporarily unavailable (os error 11)
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace
fatal runtime error: failed to initiate panic, error 5, aborting
/home/eligence/nodevenv/daily-app.eligence.dev/24/bin/node: fork: retry: Resource temporarily unavailable
/home/eligence/nodevenv/daily-app.eligence.dev/24/bin/node: fork: retry: Resource temporarily unavailable
/home/eligence/nodevenv/daily-app.eligence.dev/24/bin/node: fork: retry: Resource temporarily unavailable
/home/eligence/nodevenv/daily-app.eligence.dev/24/bin/node: fork: retry: Resource temporarily unavailable
/home/eligence/nodevenv/daily-app.eligence.dev/24/bin/node: fork: Resource temporarily unavailable
/home/eligence/nodevenv/daily-app.eligence.dev/24/bin/node: fork: retry: Resource temporarily unavailable
/home/eligence/nodevenv/daily-app.eligence.dev/24/bin/node: fork: retry: Resource temporarily unavailable
/home/eligence/nodevenv/daily-app.eligence.dev/24/bin/node: fork: retry: Resource temporarily unavailable
/home/eligence/nodevenv/daily-app.eligence.dev/24/bin/node: fork: retry: Resource temporarily unavailable

thread '<unnamed>' (1277482) panicked at /root/.cargo/registry/src/index.crates.io-1949cf8c6b5b557f/tokio-1.52.1/src/runtime/scheduler/multi_thread/worker.rs:495:13:
OS can't spawn worker thread: Resource temporarily unavailable (os error 11)
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace
fatal runtime error: failed to initiate panic, error 5, aborting

thread '<unnamed>' (1277612) panicked at /root/.cargo/registry/src/index.crates.io-1949cf8c6b5b557f/tokio-1.52.1/src/runtime/scheduler/multi_thread/worker.rs:495:13:
OS can't spawn worker thread: Resource temporarily unavailable (os error 11)
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace
fatal runtime error: failed to initiate panic, error 5, aborting

thread '<unnamed>' (1277691) panicked at /root/.cargo/registry/src/index.crates.io-1949cf8c6b5b557f/tokio-1.52.1/src/runtime/scheduler/multi_thread/worker.rs:495:13:
OS can't spawn worker thread: Resource temporarily unavailable (os error 11)
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace
fatal runtime error: failed to initiate panic, error 5, aborting

thread '<unnamed>' (1277741) panicked at /root/.cargo/registry/src/index.crates.io-1949cf8c6b5b557f/tokio-1.52.1/src/runtime/scheduler/multi_thread/worker.rs:495:13:
OS can't spawn worker thread: Resource temporarily unavailable (os error 11)
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace
fatal runtime error: failed to initiate panic, error 5, aborting

thread '<unnamed>' (1277780) panicked at /root/.cargo/registry/src/index.crates.io-1949cf8c6b5b557f/tokio-1.52.1/src/runtime/scheduler/multi_thread/worker.rs:495:13:
OS can't spawn worker thread: Resource temporarily unavailable (os error 11)
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace
fatal runtime error: failed to initiate panic, error 5, aborting

thread '<unnamed>' (1277824) panicked at /root/.cargo/registry/src/index.crates.io-1949cf8c6b5b557f/tokio-1.52.1/src/runtime/scheduler/multi_thread/worker.rs:495:13:
OS can't spawn worker thread: Resource temporarily unavailable (os error 11)
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace
fatal runtime error: failed to initiate panic, error 5, aborting

thread '<unnamed>' (1277864) panicked at /root/.cargo/registry/src/index.crates.io-1949cf8c6b5b557f/tokio-1.52.1/src/runtime/scheduler/multi_thread/worker.rs:495:13:
OS can't spawn worker thread: Resource temporarily unavailable (os error 11)
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace
fatal runtime error: failed to initiate panic, error 5, aborting

thread '<unnamed>' (1277911) panicked at /root/.cargo/registry/src/index.crates.io-1949cf8c6b5b557f/tokio-1.52.1/src/runtime/scheduler/multi_thread/worker.rs:495:13:
OS can't spawn worker thread: Resource temporarily unavailable (os error 11)
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace
fatal runtime error: failed to initiate panic, error 5, aborting

thread '<unnamed>' (1277958) panicked at /root/.cargo/registry/src/index.crates.io-1949cf8c6b5b557f/tokio-1.52.1/src/runtime/scheduler/multi_thread/worker.rs:495:13:
OS can't spawn worker thread: Resource temporarily unavailable (os error 11)
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace
fatal runtime error: failed to initiate panic, error 5, aborting

thread '<unnamed>' (1277997) panicked at /root/.cargo/registry/src/index.crates.io-1949cf8c6b5b557f/tokio-1.52.1/src/runtime/scheduler/multi_thread/worker.rs:495:13:
OS can't spawn worker thread: Resource temporarily unavailable (os error 11)
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace
fatal runtime error: failed to initiate panic, error 5, aborting

thread '<unnamed>' (1278036) panicked at /root/.cargo/registry/src/index.crates.io-1949cf8c6b5b557f/tokio-1.52.1/src/runtime/scheduler/multi_thread/worker.rs:495:13:
OS can't spawn worker thread: Resource temporarily unavailable (os error 11)
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace
fatal runtime error: failed to initiate panic, error 5, aborting
(node:1278606) [DEP0169] DeprecationWarning: `url.parse()` behavior is not standardized and prone to errors that have security implications. Use the WHATWG URL API instead. CVEs are not issued for `url.parse()` vulnerabilities.
(Use `node --trace-deprecation ...` to show where the warning was created)
(node:1278717) [DEP0169] DeprecationWarning: `url.parse()` behavior is not standardized and prone to errors that have security implications. Use the WHATWG URL API instead. CVEs are not issued for `url.parse()` vulnerabilities.
(Use `node --trace-deprecation ...` to show where the warning was created)
(node:1279101) [DEP0169] DeprecationWarning: `url.parse()` behavior is not standardized and prone to errors that have security implications. Use the WHATWG URL API instead. CVEs are not issued for `url.parse()` vulnerabilities.
(Use `node --trace-deprecation ...` to show where the warning was created)
(node:1280549) [DEP0169] DeprecationWarning: `url.parse()` behavior is not standardized and prone to errors that have security implications. Use the WHATWG URL API instead. CVEs are not issued for `url.parse()` vulnerabilities.
(Use `node --trace-deprecation ...` to show where the warning was created)
(node:1281826) [DEP0169] DeprecationWarning: `url.parse()` behavior is not standardized and prone to errors that have security implications. Use the WHATWG URL API instead. CVEs are not issued for `url.parse()` vulnerabilities.
(Use `node --trace-deprecation ...` to show where the warning was created)
(node:1282125) [DEP0169] DeprecationWarning: `url.parse()` behavior is not standardized and prone to errors that have security implications. Use the WHATWG URL API instead. CVEs are not issued for `url.parse()` vulnerabilities.
(Use `node --trace-deprecation ...` to show where the warning was created)
(node:1282243) [DEP0169] DeprecationWarning: `url.parse()` behavior is not standardized and prone to errors that have security implications. Use the WHATWG URL API instead. CVEs are not issued for `url.parse()` vulnerabilities.
(Use `node --trace-deprecation ...` to show where the warning was created)
(node:1283312) [DEP0169] DeprecationWarning: `url.parse()` behavior is not standardized and prone to errors that have security implications. Use the WHATWG URL API instead. CVEs are not issued for `url.parse()` vulnerabilities.
(Use `node --trace-deprecation ...` to show where the warning was created)
(node:1311231) [DEP0169] DeprecationWarning: `url.parse()` behavior is not standardized and prone to errors that have security implications. Use the WHATWG URL API instead. CVEs are not issued for `url.parse()` vulnerabilities.
(Use `node --trace-deprecation ...` to show where the warning was created)
(node:1320147) [DEP0169] DeprecationWarning: `url.parse()` behavior is not standardized and prone to errors that have security implications. Use the WHATWG URL API instead. CVEs are not issued for `url.parse()` vulnerabilities.
(Use `node --trace-deprecation ...` to show where the warning was created)
(node:1320629) [DEP0169] DeprecationWarning: `url.parse()` behavior is not standardized and prone to errors that have security implications. Use the WHATWG URL API instead. CVEs are not issued for `url.parse()` vulnerabilities.
(Use `node --trace-deprecation ...` to show where the warning was created)
(node:1320882) [DEP0169] DeprecationWarning: `url.parse()` behavior is not standardized and prone to errors that have security implications. Use the WHATWG URL API instead. CVEs are not issued for `url.parse()` vulnerabilities.
(Use `node --trace-deprecation ...` to show where the warning was created)
(node:1321915) [DEP0169] DeprecationWarning: `url.parse()` behavior is not standardized and prone to errors that have security implications. Use the WHATWG URL API instead. CVEs are not issued for `url.parse()` vulnerabilities.
(Use `node --trace-deprecation ...` to show where the warning was created)
(node:1322023) [DEP0169] DeprecationWarning: `url.parse()` behavior is not standardized and prone to errors that have security implications. Use the WHATWG URL API instead. CVEs are not issued for `url.parse()` vulnerabilities.
(Use `node --trace-deprecation ...` to show where the warning was created)
(node:1324254) [DEP0169] DeprecationWarning: `url.parse()` behavior is not standardized and prone to errors that have security implications. Use the WHATWG URL API instead. CVEs are not issued for `url.parse()` vulnerabilities.
(Use `node --trace-deprecation ...` to show where the warning was created)
(node:1363200) [DEP0169] DeprecationWarning: `url.parse()` behavior is not standardized and prone to errors that have security implications. Use the WHATWG URL API instead. CVEs are not issued for `url.parse()` vulnerabilities.
(Use `node --trace-deprecation ...` to show where the warning was created)
(node:1386705) [DEP0169] DeprecationWarning: `url.parse()` behavior is not standardized and prone to errors that have security implications. Use the WHATWG URL API instead. CVEs are not issued for `url.parse()` vulnerabilities.
(Use `node --trace-deprecation ...` to show where the warning was created)

thread 'tokio-runtime-worker' panicked at /root/.cargo/registry/src/index.crates.io-1949cf8c6b5b557f/futures-timer-3.0.2/src/native/delay.rs:112:21:
timer has gone away
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace
⨯ Error [PrismaClientRustPanicError]: 
Invalid `prisma.kid.findUnique()` invocation:


PANIC: timer has gone away

This is a non-recoverable error which probably happens when the Prisma Query Engine has a panic.

https://github.com/prisma/prisma/issues/new?body=Hi+Prisma+Team%21+My+Prisma+Client+just+crashed.+This+is+the+report%3A%0A%23%23+Versions%0A%0A%7C+Name++++++++++++%7C+Version++++++++++++%7C%0A%7C-----------------%7C--------------------%7C%0A%7C+Node++++++++++++%7C+v24.18.0+++++++++++%7C+%0A%7C+OS++++++++++++++%7C+debian-openssl-3.0.x%7C%0A%7C+Prisma+Client+++%7C+6.19.3+++++++++++++%7C%0A%7C+Query+Engine++++%7C+c2990dca591cba766e3b7ef5d9e8a84796e47ab7%7C%0A%7C+Database++++++++%7C+mysql++++++++++++++%7C%0A%0A%0A%0A%23%23+Logs%0A%60%60%60%0Aprisma%3AtryLoadEnv+Environment+variables+not+found+at+null%0Aprisma%3AtryLoadEnv+Environment+variables+not+found+at+undefined%0Aprisma%3AtryLoadEnv+No+Environment+variables+loaded%0Aprisma%3Aclient+checkPlatformCaching%3Apostinstall+false%0Aprisma%3Aclient+checkPlatformCaching%3AciName+%0Aprisma%3AtryLoadEnv+Environment+variables+not+found+at+null%0Aprisma%3AtryLoadEnv+Environment+variables+not+found+at+undefined%0Aprisma%3AtryLoadEnv+No+Environment+variables+loaded%0Aprisma%3Aclient+dirname+%2Fhome%2Feligence%2Fnodevenv%2Fdaily-app.eligence.dev%2F24%2Flib%2Fnode_modules%2F.prisma%2Fclient%0Aprisma%3Aclient+relativePath+..%2F..%2F..%2F..%2F..%2F..%2F..%2Fdaily-app.eligence.dev%2Fprisma%0Aprisma%3Aclient+cwd+%2Fhome%2Feligence%2Fdaily-app.eligence.dev%2Fprisma%0Aprisma%3Aclient+clientVersion+6.19.3%0Aprisma%3Aclient%3AlibraryEngine+internalSetup%0Aprisma%3Aclient%3AlibraryEngine+sending+request%2C+this.libraryStarted%3A+false%0Aprisma%3Aget-platform+Don%27t+know+any+platform-specific+paths+for+%22undefined%22+on+x64+%28x86_64%29%0Aprisma%3Aget-platform+Falling+back+to+%22ldconfig%22+and+other+generic+paths%0Aprisma%3Aget-platform+Found+libssl.so+file+using+%22ldconfig%22+or+other+generic+paths%3A+libssl.so.3%0Aprisma%3Aget-platform+The+parsed+libssl+version+is%3A+3.0.x%0Aprisma%3Aget-platform+Distro+is+%22undefined%22.+Falling+back+to+Prisma+engines+built+for+%22debian%22.%0Aprisma%3Aclient%3Aengines%3AresolveEnginePath+enginePath+%2Fhome%2Feligence%2Fnodevenv%2Fdaily-app.eligence.dev%2F24%2Flib%2Fnode_modules%2F.prisma%2Fclient%2Flibquery_engine-debian-openssl-3.0.x.so.node%0Aprisma%3Aclient%3AlibraryEngine+library+starting%0A%60%60%60%0A%0A%23%23+Client+Snippet%0A%60%60%60ts%0A%2F%2F+PLEASE+FILL+YOUR+CODE+SNIPPET+HERE%0A%60%60%60%0A%0A%23%23+Schema%0A%60%60%60prisma%0A%2F%2F+PLEASE+ADD+YOUR+SCHEMA+HERE+IF+POSSIBLE%0A%60%60%60%0A%0A%23%23+Prisma+Engine+Query%0A%60%60%60%0A%0A%60%60%60%0A&title=PANIC%3A+timer+has+gone+away&template=bug_report.yml

If you want the Prisma team to look into it, please open the link above 🙏
To increase the chance of success, please post your schema and a snippet of
how you used Prisma Client in the issue. 

    at async j (.next/server/app/kid/[loginToken]/page.js:1:6428) {
  clientVersion: '6.19.3',
  digest: '2730405554'
}

thread 'tokio-runtime-worker' panicked at /root/.cargo/registry/src/index.crates.io-1949cf8c6b5b557f/futures-timer-3.0.2/src/native/delay.rs:112:21:
timer has gone away
⨯ Error [PrismaClientRustPanicError]: 
Invalid `prisma.kid.findUnique()` invocation:


PANIC: timer has gone away

This is a non-recoverable error which probably happens when the Prisma Query Engine has a panic.

https://github.com/prisma/prisma/issues/new?body=Hi+Prisma+Team%21+My+Prisma+Client+just+crashed.+This+is+the+report%3A%0A%23%23+Versions%0A%0A%7C+Name++++++++++++%7C+Version++++++++++++%7C%0A%7C-----------------%7C--------------------%7C%0A%7C+Node++++++++++++%7C+v24.18.0+++++++++++%7C+%0A%7C+OS++++++++++++++%7C+debian-openssl-3.0.x%7C%0A%7C+Prisma+Client+++%7C+6.19.3+++++++++++++%7C%0A%7C+Query+Engine++++%7C+c2990dca591cba766e3b7ef5d9e8a84796e47ab7%7C%0A%7C+Database++++++++%7C+mysql++++++++++++++%7C%0A%0A%0A%0A%23%23+Logs%0A%60%60%60%0Aprisma%3AtryLoadEnv+Environment+variables+not+found+at+null%0Aprisma%3AtryLoadEnv+Environment+variables+not+found+at+undefined%0Aprisma%3AtryLoadEnv+No+Environment+variables+loaded%0Aprisma%3Aclient+checkPlatformCaching%3Apostinstall+false%0Aprisma%3Aclient+checkPlatformCaching%3AciName+%0Aprisma%3AtryLoadEnv+Environment+variables+not+found+at+null%0Aprisma%3AtryLoadEnv+Environment+variables+not+found+at+undefined%0Aprisma%3AtryLoadEnv+No+Environment+variables+loaded%0Aprisma%3Aclient+dirname+%2Fhome%2Feligence%2Fnodevenv%2Fdaily-app.eligence.dev%2F24%2Flib%2Fnode_modules%2F.prisma%2Fclient%0Aprisma%3Aclient+relativePath+..%2F..%2F..%2F..%2F..%2F..%2F..%2Fdaily-app.eligence.dev%2Fprisma%0Aprisma%3Aclient+cwd+%2Fhome%2Feligence%2Fdaily-app.eligence.dev%2Fprisma%0Aprisma%3Aclient+clientVersion+6.19.3%0Aprisma%3Aclient%3AlibraryEngine+internalSetup%0Aprisma%3Aclient%3AlibraryEngine+sending+request%2C+this.libraryStarted%3A+false%0Aprisma%3Aget-platform+Don%27t+know+any+platform-specific+paths+for+%22undefined%22+on+x64+%28x86_64%29%0Aprisma%3Aget-platform+Falling+back+to+%22ldconfig%22+and+other+generic+paths%0Aprisma%3Aget-platform+Found+libssl.so+file+using+%22ldconfig%22+or+other+generic+paths%3A+libssl.so.3%0Aprisma%3Aget-platform+The+parsed+libssl+version+is%3A+3.0.x%0Aprisma%3Aget-platform+Distro+is+%22undefined%22.+Falling+back+to+Prisma+engines+built+for+%22debian%22.%0Aprisma%3Aclient%3Aengines%3AresolveEnginePath+enginePath+%2Fhome%2Feligence%2Fnodevenv%2Fdaily-app.eligence.dev%2F24%2Flib%2Fnode_modules%2F.prisma%2Fclient%2Flibquery_engine-debian-openssl-3.0.x.so.node%0Aprisma%3Aclient%3AlibraryEngine+library+starting%0Aprisma%3Aclient%3Arequest_handler+%7B%22clientVersion%22%3A%226.19.3%22%2C%22name%22%3A%22PrismaClientRustPanicError%22%7D%0Aprisma%3Aclient%3AlibraryEngine+sending+request%2C+this.libraryStarted%3A+false%0Aprisma%3Aclient%3AlibraryEngine+library+starting%0A%60%60%60%0A%0A%23%23+Client+Snippet%0A%60%60%60ts%0A%2F%2F+PLEASE+FILL+YOUR+CODE+SNIPPET+HERE%0A%60%60%60%0A%0A%23%23+Schema%0A%60%60%60prisma%0A%2F%2F+PLEASE+ADD+YOUR+SCHEMA+HERE+IF+POSSIBLE%0A%60%60%60%0A%0A%23%23+Prisma+Engine+Query%0A%60%60%60%0A%0A%60%60%60%0A&title=PANIC%3A+timer+has+gone+away&template=bug_report.yml

If you want the Prisma team to look into it, please open the link above 🙏
To increase the chance of success, please post your schema and a snippet of
how you used Prisma Client in the issue. 

    at async j (.next/server/app/kid/[loginToken]/page.js:1:6428) {
  clientVersion: '6.19.3',
  digest: '3962479986'
}

thread 'tokio-runtime-worker' panicked at /root/.cargo/registry/src/index.crates.io-1949cf8c6b5b557f/futures-timer-3.0.2/src/native/delay.rs:112:21:
timer has gone away
⨯ Error [PrismaClientRustPanicError]: 
Invalid `prisma.kid.findUnique()` invocation:


PANIC: timer has gone away

This is a non-recoverable error which probably happens when the Prisma Query Engine has a panic.

https://github.com/prisma/prisma/issues/new?body=Hi+Prisma+Team%21+My+Prisma+Client+just+crashed.+This+is+the+report%3A%0A%23%23+Versions%0A%0A%7C+Name++++++++++++%7C+Version++++++++++++%7C%0A%7C-----------------%7C--------------------%7C%0A%7C+Node++++++++++++%7C+v24.18.0+++++++++++%7C+%0A%7C+OS++++++++++++++%7C+debian-openssl-3.0.x%7C%0A%7C+Prisma+Client+++%7C+6.19.3+++++++++++++%7C%0A%7C+Query+Engine++++%7C+c2990dca591cba766e3b7ef5d9e8a84796e47ab7%7C%0A%7C+Database++++++++%7C+mysql++++++++++++++%7C%0A%0A%0A%0A%23%23+Logs%0A%60%60%60%0Aprisma%3AtryLoadEnv+Environment+variables+not+found+at+null%0Aprisma%3AtryLoadEnv+Environment+variables+not+found+at+undefined%0Aprisma%3AtryLoadEnv+No+Environment+variables+loaded%0Aprisma%3Aclient+checkPlatformCaching%3Apostinstall+false%0Aprisma%3Aclient+checkPlatformCaching%3AciName+%0Aprisma%3AtryLoadEnv+Environment+variables+not+found+at+null%0Aprisma%3AtryLoadEnv+Environment+variables+not+found+at+undefined%0Aprisma%3AtryLoadEnv+No+Environment+variables+loaded%0Aprisma%3Aclient+dirname+%2Fhome%2Feligence%2Fnodevenv%2Fdaily-app.eligence.dev%2F24%2Flib%2Fnode_modules%2F.prisma%2Fclient%0Aprisma%3Aclient+relativePath+..%2F..%2F..%2F..%2F..%2F..%2F..%2Fdaily-app.eligence.dev%2Fprisma%0Aprisma%3Aclient+cwd+%2Fhome%2Feligence%2Fdaily-app.eligence.dev%2Fprisma%0Aprisma%3Aclient+clientVersion+6.19.3%0Aprisma%3Aclient%3AlibraryEngine+internalSetup%0Aprisma%3Aclient%3AlibraryEngine+sending+request%2C+this.libraryStarted%3A+false%0Aprisma%3Aget-platform+Don%27t+know+any+platform-specific+paths+for+%22undefined%22+on+x64+%28x86_64%29%0Aprisma%3Aget-platform+Falling+back+to+%22ldconfig%22+and+other+generic+paths%0Aprisma%3Aget-platform+Found+libssl.so+file+using+%22ldconfig%22+or+other+generic+paths%3A+libssl.so.3%0Aprisma%3Aget-platform+The+parsed+libssl+version+is%3A+3.0.x%0Aprisma%3Aget-platform+Distro+is+%22undefined%22.+Falling+back+to+Prisma+engines+built+for+%22debian%22.%0Aprisma%3Aclient%3Aengines%3AresolveEnginePath+enginePath+%2Fhome%2Feligence%2Fnodevenv%2Fdaily-app.eligence.dev%2F24%2Flib%2Fnode_modules%2F.prisma%2Fclient%2Flibquery_engine-debian-openssl-3.0.x.so.node%0Aprisma%3Aclient%3AlibraryEngine+library+starting%0Aprisma%3Aclient%3Arequest_handler+%7B%22clientVersion%22%3A%226.19.3%22%2C%22name%22%3A%22PrismaClientRustPanicError%22%7D%0Aprisma%3Aclient%3AlibraryEngine+sending+request%2C+this.libraryStarted%3A+false%0Aprisma%3Aclient%3AlibraryEngine+library+starting%0Aprisma%3Aclient%3Arequest_handler+%7B%22clientVersion%22%3A%226.19.3%22%2C%22name%22%3A%22PrismaClientRustPanicError%22%7D%0Aprisma%3Aclient%3AlibraryEngine+sending+request%2C+this.libraryStarted%3A+false%0Aprisma%3Aclient%3AlibraryEngine+library+starting%0A%60%60%60%0A%0A%23%23+Client+Snippet%0A%60%60%60ts%0A%2F%2F+PLEASE+FILL+YOUR+CODE+SNIPPET+HERE%0A%60%60%60%0A%0A%23%23+Schema%0A%60%60%60prisma%0A%2F%2F+PLEASE+ADD+YOUR+SCHEMA+HERE+IF+POSSIBLE%0A%60%60%60%0A%0A%23%23+Prisma+Engine+Query%0A%60%60%60%0A%0A%60%60%60%0A&title=PANIC%3A+timer+has+gone+away&template=bug_report.yml

If you want the Prisma team to look into it, please open the link above 🙏
To increase the chance of success, please post your schema and a snippet of
how you used Prisma Client in the issue. 

    at async j (.next/server/app/kid/[loginToken]/page.js:1:6428) {
  clientVersion: '6.19.3',
  digest: '2846001458'
}

thread 'tokio-runtime-worker' panicked at /root/.cargo/registry/src/index.crates.io-1949cf8c6b5b557f/futures-timer-3.0.2/src/native/delay.rs:112:21:
timer has gone away
⨯ Error [PrismaClientRustPanicError]: 
Invalid `prisma.user.findUnique()` invocation:


PANIC: timer has gone away

This is a non-recoverable error which probably happens when the Prisma Query Engine has a panic.

https://github.com/prisma/prisma/issues/new?body=Hi+Prisma+Team%21+My+Prisma+Client+just+crashed.+This+is+the+report%3A%0A%23%23+Versions%0A%0A%7C+Name++++++++++++%7C+Version++++++++++++%7C%0A%7C-----------------%7C--------------------%7C%0A%7C+Node++++++++++++%7C+v24.18.0+++++++++++%7C+%0A%7C+OS++++++++++++++%7C+debian-openssl-3.0.x%7C%0A%7C+Prisma+Client+++%7C+6.19.3+++++++++++++%7C%0A%7C+Query+Engine++++%7C+c2990dca591cba766e3b7ef5d9e8a84796e47ab7%7C%0A%7C+Database++++++++%7C+mysql++++++++++++++%7C%0A%0A%0A%0A%23%23+Logs%0A%60%60%60%0Aprisma%3AtryLoadEnv+Environment+variables+not+found+at+null%0Aprisma%3AtryLoadEnv+Environment+variables+not+found+at+undefined%0Aprisma%3AtryLoadEnv+No+Environment+variables+loaded%0Aprisma%3Aclient+checkPlatformCaching%3Apostinstall+false%0Aprisma%3Aclient+checkPlatformCaching%3AciName+%0Aprisma%3AtryLoadEnv+Environment+variables+not+found+at+null%0Aprisma%3AtryLoadEnv+Environment+variables+not+found+at+undefined%0Aprisma%3AtryLoadEnv+No+Environment+variables+loaded%0Aprisma%3Aclient+dirname+%2Fhome%2Feligence%2Fnodevenv%2Fdaily-app.eligence.dev%2F24%2Flib%2Fnode_modules%2F.prisma%2Fclient%0Aprisma%3Aclient+relativePath+..%2F..%2F..%2F..%2F..%2F..%2F..%2Fdaily-app.eligence.dev%2Fprisma%0Aprisma%3Aclient+cwd+%2Fhome%2Feligence%2Fdaily-app.eligence.dev%2Fprisma%0Aprisma%3Aclient+clientVersion+6.19.3%0Aprisma%3Aclient%3AlibraryEngine+internalSetup%0Aprisma%3Aclient%3AlibraryEngine+sending+request%2C+this.libraryStarted%3A+false%0Aprisma%3Aget-platform+Don%27t+know+any+platform-specific+paths+for+%22undefined%22+on+x64+%28x86_64%29%0Aprisma%3Aget-platform+Falling+back+to+%22ldconfig%22+and+other+generic+paths%0Aprisma%3Aget-platform+Found+libssl.so+file+using+%22ldconfig%22+or+other+generic+paths%3A+libssl.so.3%0Aprisma%3Aget-platform+The+parsed+libssl+version+is%3A+3.0.x%0Aprisma%3Aget-platform+Distro+is+%22undefined%22.+Falling+back+to+Prisma+engines+built+for+%22debian%22.%0Aprisma%3Aclient%3Aengines%3AresolveEnginePath+enginePath+%2Fhome%2Feligence%2Fnodevenv%2Fdaily-app.eligence.dev%2F24%2Flib%2Fnode_modules%2F.prisma%2Fclient%2Flibquery_engine-debian-openssl-3.0.x.so.node%0Aprisma%3Aclient%3AlibraryEngine+library+starting%0Aprisma%3Aclient%3Arequest_handler+%7B%22clientVersion%22%3A%226.19.3%22%2C%22name%22%3A%22PrismaClientRustPanicError%22%7D%0Aprisma%3Aclient%3AlibraryEngine+sending+request%2C+this.libraryStarted%3A+false%0Aprisma%3Aclient%3AlibraryEngine+library+starting%0Aprisma%3Aclient%3Arequest_handler+%7B%22clientVersion%22%3A%226.19.3%22%2C%22name%22%3A%22PrismaClientRustPanicError%22%7D%0Aprisma%3Aclient%3AlibraryEngine+sending+request%2C+this.libraryStarted%3A+false%0Aprisma%3Aclient%3AlibraryEngine+library+starting%0Aprisma%3Aclient%3Arequest_handler+%7B%22clientVersion%22%3A%226.19.3%22%2C%22name%22%3A%22PrismaClientRustPanicError%22%7D%0Aprisma%3Aclient%3AlibraryEngine+sending+request%2C+this.libraryStarted%3A+false%0Aprisma%3Aclient%3AlibraryEngine+library+starting%0A%60%60%60%0A%0A%23%23+Client+Snippet%0A%60%60%60ts%0A%2F%2F+PLEASE+FILL+YOUR+CODE+SNIPPET+HERE%0A%60%60%60%0A%0A%23%23+Schema%0A%60%60%60prisma%0A%2F%2F+PLEASE+ADD+YOUR+SCHEMA+HERE+IF+POSSIBLE%0A%60%60%60%0A%0A%23%23+Prisma+Engine+Query%0A%60%60%60%0A%0A%60%60%60%0A&title=PANIC%3A+timer+has+gone+away&template=bug_report.yml

If you want the Prisma team to look into it, please open the link above 🙏
To increase the chance of success, please post your schema and a snippet of
how you used Prisma Client in the issue. 

    at async n (.next/server/app/parent/page.js:1:7076)
    at async k (.next/server/app/parent/page.js:2:51095) {
  clientVersion: '6.19.3',
  digest: '3580523186'
}

thread 'tokio-runtime-worker' panicked at /root/.cargo/registry/src/index.crates.io-1949cf8c6b5b557f/futures-timer-3.0.2/src/native/delay.rs:112:21:
timer has gone away
⨯ Error [PrismaClientRustPanicError]: 
Invalid `prisma.user.findUnique()` invocation:


PANIC: timer has gone away

This is a non-recoverable error which probably happens when the Prisma Query Engine has a panic.

https://github.com/prisma/prisma/issues/new?body=Hi+Prisma+Team%21+My+Prisma+Client+just+crashed.+This+is+the+report%3A%0A%23%23+Versions%0A%0A%7C+Name++++++++++++%7C+Version++++++++++++%7C%0A%7C-----------------%7C--------------------%7C%0A%7C+Node++++++++++++%7C+v24.18.0+++++++++++%7C+%0A%7C+OS++++++++++++++%7C+debian-openssl-3.0.x%7C%0A%7C+Prisma+Client+++%7C+6.19.3+++++++++++++%7C%0A%7C+Query+Engine++++%7C+c2990dca591cba766e3b7ef5d9e8a84796e47ab7%7C%0A%7C+Database++++++++%7C+mysql++++++++++++++%7C%0A%0A%0A%0A%23%23+Logs%0A%60%60%60%0Aprisma%3AtryLoadEnv+Environment+variables+not+found+at+null%0Aprisma%3AtryLoadEnv+Environment+variables+not+found+at+undefined%0Aprisma%3AtryLoadEnv+No+Environment+variables+loaded%0Aprisma%3Aclient+checkPlatformCaching%3Apostinstall+false%0Aprisma%3Aclient+checkPlatformCaching%3AciName+%0Aprisma%3AtryLoadEnv+Environment+variables+not+found+at+null%0Aprisma%3AtryLoadEnv+Environment+variables+not+found+at+undefined%0Aprisma%3AtryLoadEnv+No+Environment+variables+loaded%0Aprisma%3Aclient+dirname+%2Fhome%2Feligence%2Fnodevenv%2Fdaily-app.eligence.dev%2F24%2Flib%2Fnode_modules%2F.prisma%2Fclient%0Aprisma%3Aclient+relativePath+..%2F..%2F..%2F..%2F..%2F..%2F..%2Fdaily-app.eligence.dev%2Fprisma%0Aprisma%3Aclient+cwd+%2Fhome%2Feligence%2Fdaily-app.eligence.dev%2Fprisma%0Aprisma%3Aclient+clientVersion+6.19.3%0Aprisma%3Aclient%3AlibraryEngine+internalSetup%0Aprisma%3Aclient%3AlibraryEngine+sending+request%2C+this.libraryStarted%3A+false%0Aprisma%3Aget-platform+Don%27t+know+any+platform-specific+paths+for+%22undefined%22+on+x64+%28x86_64%29%0Aprisma%3Aget-platform+Falling+back+to+%22ldconfig%22+and+other+generic+paths%0Aprisma%3Aget-platform+Found+libssl.so+file+using+%22ldconfig%22+or+other+generic+paths%3A+libssl.so.3%0Aprisma%3Aget-platform+The+parsed+libssl+version+is%3A+3.0.x%0Aprisma%3Aget-platform+Distro+is+%22undefined%22.+Falling+back+to+Prisma+engines+built+for+%22debian%22.%0Aprisma%3Aclient%3Aengines%3AresolveEnginePath+enginePath+%2Fhome%2Feligence%2Fnodevenv%2Fdaily-app.eligence.dev%2F24%2Flib%2Fnode_modules%2F.prisma%2Fclient%2Flibquery_engine-debian-openssl-3.0.x.so.node%0Aprisma%3Aclient%3AlibraryEngine+library+starting%0Aprisma%3Aclient%3Arequest_handler+%7B%22clientVersion%22%3A%226.19.3%22%2C%22name%22%3A%22PrismaClientRustPanicError%22%7D%0Aprisma%3Aclient%3AlibraryEngine+sending+request%2C+this.libraryStarted%3A+false%0Aprisma%3Aclient%3AlibraryEngine+library+starting%0Aprisma%3Aclient%3Arequest_handler+%7B%22clientVersion%22%3A%226.19.3%22%2C%22name%22%3A%22PrismaClientRustPanicError%22%7D%0Aprisma%3Aclient%3AlibraryEngine+sending+request%2C+this.libraryStarted%3A+false%0Aprisma%3Aclient%3AlibraryEngine+library+starting%0Aprisma%3Aclient%3Arequest_handler+%7B%22clientVersion%22%3A%226.19.3%22%2C%22name%22%3A%22PrismaClientRustPanicError%22%7D%0Aprisma%3Aclient%3AlibraryEngine+sending+request%2C+this.libraryStarted%3A+false%0Aprisma%3Aclient%3AlibraryEngine+library+starting%0Aprisma%3Aclient%3Arequest_handler+%7B%22clientVersion%22%3A%226.19.3%22%2C%22name%22%3A%22PrismaClientRustPanicError%22%7D%0Aprisma%3Aclient%3AlibraryEngine+sending+request%2C+this.libraryStarted%3A+false%0Aprisma%3Aclient%3AlibraryEngine+library+starting%0A%60%60%60%0A%0A%23%23+Client+Snippet%0A%60%60%60ts%0A%2F%2F+PLEASE+FILL+YOUR+CODE+SNIPPET+HERE%0A%60%60%60%0A%0A%23%23+Schema%0A%60%60%60prisma%0A%2F%2F+PLEASE+ADD+YOUR+SCHEMA+HERE+IF+POSSIBLE%0A%60%60%60%0A%0A%23%23+Prisma+Engine+Query%0A%60%60%60%0A%0A%60%60%60%0A&title=PANIC%3A+timer+has+gone+away&template=bug_report.yml

If you want the Prisma team to look into it, please open the link above 🙏
To increase the chance of success, please post your schema and a snippet of
how you used Prisma Client in the issue. 

    at async n (.next/server/app/parent/page.js:1:7076)
    at async k (.next/server/app/parent/page.js:2:51095) {
  clientVersion: '6.19.3',
  digest: '2460388306'
}
(node:1497298) [DEP0169] DeprecationWarning: `url.parse()` behavior is not standardized and prone to errors that have security implications. Use the WHATWG URL API instead. CVEs are not issued for `url.parse()` vulnerabilities.
(Use `node --trace-deprecation ...` to show where the warning was created)

thread 'tokio-runtime-worker' panicked at /root/.cargo/registry/src/index.crates.io-1949cf8c6b5b557f/futures-timer-3.0.2/src/native/delay.rs:112:21:
timer has gone away
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace
⨯ Error [PrismaClientRustPanicError]: 
Invalid `prisma.user.findUnique()` invocation:


PANIC: timer has gone away

This is a non-recoverable error which probably happens when the Prisma Query Engine has a panic.

https://github.com/prisma/prisma/issues/new?body=Hi+Prisma+Team%21+My+Prisma+Client+just+crashed.+This+is+the+report%3A%0A%23%23+Versions%0A%0A%7C+Name++++++++++++%7C+Version++++++++++++%7C%0A%7C-----------------%7C--------------------%7C%0A%7C+Node++++++++++++%7C+v24.18.0+++++++++++%7C+%0A%7C+OS++++++++++++++%7C+debian-openssl-3.0.x%7C%0A%7C+Prisma+Client+++%7C+6.19.3+++++++++++++%7C%0A%7C+Query+Engine++++%7C+c2990dca591cba766e3b7ef5d9e8a84796e47ab7%7C%0A%7C+Database++++++++%7C+mysql++++++++++++++%7C%0A%0A%0A%0A%23%23+Logs%0A%60%60%60%0Aprisma%3AtryLoadEnv+Environment+variables+not+found+at+null%0Aprisma%3AtryLoadEnv+Environment+variables+not+found+at+undefined%0Aprisma%3AtryLoadEnv+No+Environment+variables+loaded%0Aprisma%3Aclient+checkPlatformCaching%3Apostinstall+false%0Aprisma%3Aclient+checkPlatformCaching%3AciName+%0Aprisma%3AtryLoadEnv+Environment+variables+not+found+at+null%0Aprisma%3AtryLoadEnv+Environment+variables+not+found+at+undefined%0Aprisma%3AtryLoadEnv+No+Environment+variables+loaded%0Aprisma%3Aclient+dirname+%2Fhome%2Feligence%2Fnodevenv%2Fdaily-app.eligence.dev%2F24%2Flib%2Fnode_modules%2F.prisma%2Fclient%0Aprisma%3Aclient+relativePath+..%2F..%2F..%2F..%2F..%2F..%2F..%2Fdaily-app.eligence.dev%2Fprisma%0Aprisma%3Aclient+cwd+%2Fhome%2Feligence%2Fdaily-app.eligence.dev%2Fprisma%0Aprisma%3Aclient+clientVersion+6.19.3%0Aprisma%3Aclient%3AlibraryEngine+internalSetup%0Aprisma%3Aget-platform+Don%27t+know+any+platform-specific+paths+for+%22undefined%22+on+x64+%28x86_64%29%0Aprisma%3Aget-platform+Falling+back+to+%22ldconfig%22+and+other+generic+paths%0Aprisma%3Aclient%3AlibraryEngine+sending+request%2C+this.libraryStarted%3A+false%0Aprisma%3Aget-platform+Found+libssl.so+file+using+%22ldconfig%22+or+other+generic+paths%3A+libssl.so.3%0Aprisma%3Aget-platform+The+parsed+libssl+version+is%3A+3.0.x%0Aprisma%3Aget-platform+Distro+is+%22undefined%22.+Falling+back+to+Prisma+engines+built+for+%22debian%22.%0Aprisma%3Aclient%3Aengines%3AresolveEnginePath+enginePath+%2Fhome%2Feligence%2Fnodevenv%2Fdaily-app.eligence.dev%2F24%2Flib%2Fnode_modules%2F.prisma%2Fclient%2Flibquery_engine-debian-openssl-3.0.x.so.node%0Aprisma%3Aclient%3AlibraryEngine+library+starting%0A%60%60%60%0A%0A%23%23+Client+Snippet%0A%60%60%60ts%0A%2F%2F+PLEASE+FILL+YOUR+CODE+SNIPPET+HERE%0A%60%60%60%0A%0A%23%23+Schema%0A%60%60%60prisma%0A%2F%2F+PLEASE+ADD+YOUR+SCHEMA+HERE+IF+POSSIBLE%0A%60%60%60%0A%0A%23%23+Prisma+Engine+Query%0A%60%60%60%0A%0A%60%60%60%0A&title=PANIC%3A+timer+has+gone+away&template=bug_report.yml

If you want the Prisma team to look into it, please open the link above 🙏
To increase the chance of success, please post your schema and a snippet of
how you used Prisma Client in the issue. 

    at async n (.next/server/app/parent/page.js:1:7076)
    at async k (.next/server/app/parent/page.js:2:51095) {
  clientVersion: '6.19.3',
  digest: '3569970514'
}
/home/eligence/nodevenv/daily-app.eligence.dev/24/bin/node: fork: retry: Resource temporarily unavailable
/home/eligence/nodevenv/daily-app.eligence.dev/24/bin/node: fork: retry: Resource temporarily unavailable
/home/eligence/nodevenv/daily-app.eligence.dev/24/bin/node: fork: retry: Resource temporarily unavailable
/home/eligence/nodevenv/daily-app.eligence.dev/24/bin/node: fork: retry: Resource temporarily unavailable
/home/eligence/nodevenv/daily-app.eligence.dev/24/bin/node: fork: Resource temporarily unavailable
/home/eligence/nodevenv/daily-app.eligence.dev/24/bin/node: fork: retry: Resource temporarily unavailable
/home/eligence/nodevenv/daily-app.eligence.dev/24/bin/node: fork: retry: Resource temporarily unavailable
/home/eligence/nodevenv/daily-app.eligence.dev/24/bin/node: fork: retry: Resource temporarily unavailable
/home/eligence/nodevenv/daily-app.eligence.dev/24/bin/node: fork: retry: Resource temporarily unavailable
/home/eligence/nodevenv/daily-app.eligence.dev/24/bin/node: fork: Resource temporarily unavailable
/home/eligence/nodevenv/daily-app.eligence.dev/24/bin/node: fork: retry: Resource temporarily unavailable
/home/eligence/nodevenv/daily-app.eligence.dev/24/bin/node: fork: retry: Resource temporarily unavailable
/home/eligence/nodevenv/daily-app.eligence.dev/24/bin/node: fork: retry: Resource temporarily unavailable
/home/eligence/nodevenv/daily-app.eligence.dev/24/bin/node: fork: retry: Resource temporarily unavailable
/home/eligence/nodevenv/daily-app.eligence.dev/24/bin/node: fork: Resource temporarily unavailable
/home/eligence/nodevenv/daily-app.eligence.dev/24/bin/node: fork: retry: Resource temporarily unavailable
/home/eligence/nodevenv/daily-app.eligence.dev/24/bin/node: fork: retry: Resource temporarily unavailable
/home/eligence/nodevenv/daily-app.eligence.dev/24/bin/node: fork: retry: Resource temporarily unavailable
/home/eligence/nodevenv/daily-app.eligence.dev/24/bin/node: fork: retry: Resource temporarily unavailable
/home/eligence/nodevenv/daily-app.eligence.dev/24/bin/node: fork: Resource temporarily unavailable
/home/eligence/nodevenv/daily-app.eligence.dev/24/bin/node: fork: retry: Resource temporarily unavailable
/home/eligence/nodevenv/daily-app.eligence.dev/24/bin/node: fork: retry: Resource temporarily unavailable
/home/eligence/nodevenv/daily-app.eligence.dev/24/bin/node: fork: retry: Resource temporarily unavailable
/home/eligence/nodevenv/daily-app.eligence.dev/24/bin/node: fork: retry: Resource temporarily unavailable
/home/eligence/nodevenv/daily-app.eligence.dev/24/bin/node: fork: Resource temporarily unavailable
/home/eligence/nodevenv/daily-app.eligence.dev/24/bin/node: fork: retry: Resource temporarily unavailable
/home/eligence/nodevenv/daily-app.eligence.dev/24/bin/node: fork: retry: Resource temporarily unavailable
/home/eligence/nodevenv/daily-app.eligence.dev/24/bin/node: fork: retry: Resource temporarily unavailable
/home/eligence/nodevenv/daily-app.eligence.dev/24/bin/node: fork: retry: Resource temporarily unavailable
/home/eligence/nodevenv/daily-app.eligence.dev/24/bin/node: fork: Resource temporarily unavailable
/home/eligence/nodevenv/daily-app.eligence.dev/24/bin/node: fork: retry: Resource temporarily unavailable
/home/eligence/nodevenv/daily-app.eligence.dev/24/bin/node: fork: retry: Resource temporarily unavailable
/home/eligence/nodevenv/daily-app.eligence.dev/24/bin/node: fork: retry: Resource temporarily unavailable
/home/eligence/nodevenv/daily-app.eligence.dev/24/bin/node: fork: retry: Resource temporarily unavailable
/home/eligence/nodevenv/daily-app.eligence.dev/24/bin/node: fork: Resource temporarily unavailable
/home/eligence/nodevenv/daily-app.eligence.dev/24/bin/node: fork: retry: Resource temporarily unavailable
/home/eligence/nodevenv/daily-app.eligence.dev/24/bin/node: fork: retry: Resource temporarily unavailable
/home/eligence/nodevenv/daily-app.eligence.dev/24/bin/node: fork: retry: Resource temporarily unavailable
/home/eligence/nodevenv/daily-app.eligence.dev/24/bin/node: fork: retry: Resource temporarily unavailable
/home/eligence/nodevenv/daily-app.eligence.dev/24/bin/node: fork: Resource temporarily unavailable
/home/eligence/nodevenv/daily-app.eligence.dev/24/bin/node: fork: retry: Resource temporarily unavailable
/home/eligence/nodevenv/daily-app.eligence.dev/24/bin/node: fork: retry: Resource temporarily unavailable
/home/eligence/nodevenv/daily-app.eligence.dev/24/bin/node: fork: retry: Resource temporarily unavailable
/home/eligence/nodevenv/daily-app.eligence.dev/24/bin/node: fork: retry: Resource temporarily unavailable
/home/eligence/nodevenv/daily-app.eligence.dev/24/bin/node: fork: Resource temporarily unavailable
/home/eligence/nodevenv/daily-app.eligence.dev/24/bin/node: fork: retry: Resource temporarily unavailable
/home/eligence/nodevenv/daily-app.eligence.dev/24/bin/node: fork: retry: Resource temporarily unavailable
/home/eligence/nodevenv/daily-app.eligence.dev/24/bin/node: fork: retry: Resource temporarily unavailable
/home/eligence/nodevenv/daily-app.eligence.dev/24/bin/node: fork: retry: Resource temporarily unavailable
/home/eligence/nodevenv/daily-app.eligence.dev/24/bin/node: fork: Resource temporarily unavailable
/home/eligence/nodevenv/daily-app.eligence.dev/24/bin/node: fork: retry: Resource temporarily unavailable
/home/eligence/nodevenv/daily-app.eligence.dev/24/bin/node: fork: retry: Resource temporarily unavailable
/home/eligence/nodevenv/daily-app.eligence.dev/24/bin/node: fork: retry: Resource temporarily unavailable
/home/eligence/nodevenv/daily-app.eligence.dev/24/bin/node: fork: retry: Resource temporarily unavailable
/home/eligence/nodevenv/daily-app.eligence.dev/24/bin/node: fork: Resource temporarily unavailable
/home/eligence/nodevenv/daily-app.eligence.dev/24/bin/node: fork: retry: Resource temporarily unavailable
/home/eligence/nodevenv/daily-app.eligence.dev/24/bin/node: fork: retry: Resource temporarily unavailable
/home/eligence/nodevenv/daily-app.eligence.dev/24/bin/node: fork: retry: Resource temporarily unavailable
/home/eligence/nodevenv/daily-app.eligence.dev/24/bin/node: fork: retry: Resource temporarily unavailable
/home/eligence/nodevenv/daily-app.eligence.dev/24/bin/node: fork: Resource temporarily unavailable
/home/eligence/nodevenv/daily-app.eligence.dev/24/bin/node: fork: retry: Resource temporarily unavailable
/home/eligence/nodevenv/daily-app.eligence.dev/24/bin/node: fork: retry: Resource temporarily unavailable
/home/eligence/nodevenv/daily-app.eligence.dev/24/bin/node: fork: retry: Resource temporarily unavailable
/home/eligence/nodevenv/daily-app.eligence.dev/24/bin/node: fork: retry: Resource temporarily unavailable
/home/eligence/nodevenv/daily-app.eligence.dev/24/bin/node: fork: Resource temporarily unavailable
/home/eligence/nodevenv/daily-app.eligence.dev/24/bin/node: fork: retry: Resource temporarily unavailable
/home/eligence/nodevenv/daily-app.eligence.dev/24/bin/node: fork: retry: Resource temporarily unavailable
/home/eligence/nodevenv/daily-app.eligence.dev/24/bin/node: fork: retry: Resource temporarily unavailable
/home/eligence/nodevenv/daily-app.eligence.dev/24/bin/node: fork: retry: Resource temporarily unavailable
/home/eligence/nodevenv/daily-app.eligence.dev/24/bin/node: fork: Resource temporarily unavailable
/home/eligence/nodevenv/daily-app.eligence.dev/24/bin/node: fork: retry: Resource temporarily unavailable
/home/eligence/nodevenv/daily-app.eligence.dev/24/bin/node: fork: retry: Resource temporarily unavailable
/home/eligence/nodevenv/daily-app.eligence.dev/24/bin/node: fork: retry: Resource temporarily unavailable
/home/eligence/nodevenv/daily-app.eligence.dev/24/bin/node: fork: retry: Resource temporarily unavailable
/home/eligence/nodevenv/daily-app.eligence.dev/24/bin/node: fork: Resource temporarily unavailable
/home/eligence/nodevenv/daily-app.eligence.dev/24/bin/node: fork: retry: Resource temporarily unavailable
/home/eligence/nodevenv/daily-app.eligence.dev/24/bin/node: fork: retry: Resource temporarily unavailable
/home/eligence/nodevenv/daily-app.eligence.dev/24/bin/node: fork: retry: Resource temporarily unavailable
/home/eligence/nodevenv/daily-app.eligence.dev/24/bin/node: fork: retry: Resource temporarily unavailable
/home/eligence/nodevenv/daily-app.eligence.dev/24/bin/node: fork: Resource temporarily unavailable
/home/eligence/nodevenv/daily-app.eligence.dev/24/bin/node: fork: retry: Resource temporarily unavailable
/home/eligence/nodevenv/daily-app.eligence.dev/24/bin/node: fork: retry: Resource temporarily unavailable
/home/eligence/nodevenv/daily-app.eligence.dev/24/bin/node: fork: retry: Resource temporarily unavailable
/home/eligence/nodevenv/daily-app.eligence.dev/24/bin/node: fork: retry: Resource temporarily unavailable
/home/eligence/nodevenv/daily-app.eligence.dev/24/bin/node: fork: Resource temporarily unavailable
/home/eligence/nodevenv/daily-app.eligence.dev/24/bin/node: fork: retry: Resource temporarily unavailable
/home/eligence/nodevenv/daily-app.eligence.dev/24/bin/node: fork: retry: Resource temporarily unavailable
/home/eligence/nodevenv/daily-app.eligence.dev/24/bin/node: fork: retry: Resource temporarily unavailable
/home/eligence/nodevenv/daily-app.eligence.dev/24/bin/node: fork: retry: Resource temporarily unavailable
/home/eligence/nodevenv/daily-app.eligence.dev/24/bin/node: fork: Resource temporarily unavailable
/home/eligence/nodevenv/daily-app.eligence.dev/24/bin/node: fork: retry: Resource temporarily unavailable
/home/eligence/nodevenv/daily-app.eligence.dev/24/bin/node: fork: retry: Resource temporarily unavailable
/home/eligence/nodevenv/daily-app.eligence.dev/24/bin/node: fork: retry: Resource temporarily unavailable
/home/eligence/nodevenv/daily-app.eligence.dev/24/bin/node: fork: retry: Resource temporarily unavailable
/home/eligence/nodevenv/daily-app.eligence.dev/24/bin/node: fork: Resource temporarily unavailable
/home/eligence/nodevenv/daily-app.eligence.dev/24/bin/node: fork: retry: Resource temporarily unavailable
/home/eligence/nodevenv/daily-app.eligence.dev/24/bin/node: fork: retry: Resource temporarily unavailable
/home/eligence/nodevenv/daily-app.eligence.dev/24/bin/node: fork: retry: Resource temporarily unavailable
/home/eligence/nodevenv/daily-app.eligence.dev/24/bin/node: fork: retry: Resource temporarily unavailable
/home/eligence/nodevenv/daily-app.eligence.dev/24/bin/node: fork: Resource temporarily unavailable
/home/eligence/nodevenv/daily-app.eligence.dev/24/bin/node: fork: retry: Resource temporarily unavailable
/home/eligence/nodevenv/daily-app.eligence.dev/24/bin/node: fork: retry: Resource temporarily unavailable
/home/eligence/nodevenv/daily-app.eligence.dev/24/bin/node: fork: retry: Resource temporarily unavailable
/home/eligence/nodevenv/daily-app.eligence.dev/24/bin/node: fork: retry: Resource temporarily unavailable
/home/eligence/nodevenv/daily-app.eligence.dev/24/bin/node: fork: Resource temporarily unavailable
/home/eligence/nodevenv/daily-app.eligence.dev/24/bin/node: fork: retry: Resource temporarily unavailable
/home/eligence/nodevenv/daily-app.eligence.dev/24/bin/node: fork: retry: Resource temporarily unavailable
/home/eligence/nodevenv/daily-app.eligence.dev/24/bin/node: fork: retry: Resource temporarily unavailable
/home/eligence/nodevenv/daily-app.eligence.dev/24/bin/node: fork: retry: Resource temporarily unavailable
/home/eligence/nodevenv/daily-app.eligence.dev/24/bin/node: fork: Resource temporarily unavailable
/home/eligence/nodevenv/daily-app.eligence.dev/24/bin/node: fork: retry: Resource temporarily unavailable
/home/eligence/nodevenv/daily-app.eligence.dev/24/bin/node: fork: retry: Resource temporarily unavailable
/home/eligence/nodevenv/daily-app.eligence.dev/24/bin/node: fork: retry: Resource temporarily unavailable
/home/eligence/nodevenv/daily-app.eligence.dev/24/bin/node: fork: retry: Resource temporarily unavailable
/home/eligence/nodevenv/daily-app.eligence.dev/24/bin/node: fork: Resource temporarily unavailable
/home/eligence/nodevenv/daily-app.eligence.dev/24/bin/node: fork: retry: Resource temporarily unavailable
/home/eligence/nodevenv/daily-app.eligence.dev/24/bin/node: fork: retry: Resource temporarily unavailable
/home/eligence/nodevenv/daily-app.eligence.dev/24/bin/node: fork: retry: Resource temporarily unavailable
/home/eligence/nodevenv/daily-app.eligence.dev/24/bin/node: fork: retry: Resource temporarily unavailable
/home/eligence/nodevenv/daily-app.eligence.dev/24/bin/node: fork: Resource temporarily unavailable
/home/eligence/nodevenv/daily-app.eligence.dev/24/bin/node: fork: retry: Resource temporarily unavailable
/home/eligence/nodevenv/daily-app.eligence.dev/24/bin/node: fork: retry: Resource temporarily unavailable
/home/eligence/nodevenv/daily-app.eligence.dev/24/bin/node: fork: retry: Resource temporarily unavailable
/home/eligence/nodevenv/daily-app.eligence.dev/24/bin/node: fork: retry: Resource temporarily unavailable
/home/eligence/nodevenv/daily-app.eligence.dev/24/bin/node: fork: Resource temporarily unavailable
/home/eligence/nodevenv/daily-app.eligence.dev/24/bin/node: fork: retry: Resource temporarily unavailable
/home/eligence/nodevenv/daily-app.eligence.dev/24/bin/node: fork: retry: Resource temporarily unavailable
/home/eligence/nodevenv/daily-app.eligence.dev/24/bin/node: fork: retry: Resource temporarily unavailable
/home/eligence/nodevenv/daily-app.eligence.dev/24/bin/node: fork: retry: Resource temporarily unavailable
/home/eligence/nodevenv/daily-app.eligence.dev/24/bin/node: fork: Resource temporarily unavailable
/home/eligence/nodevenv/daily-app.eligence.dev/24/bin/node: fork: retry: Resource temporarily unavailable
/home/eligence/nodevenv/daily-app.eligence.dev/24/bin/node: fork: retry: Resource temporarily unavailable
/home/eligence/nodevenv/daily-app.eligence.dev/24/bin/node: fork: retry: Resource temporarily unavailable
/home/eligence/nodevenv/daily-app.eligence.dev/24/bin/node: fork: retry: Resource temporarily unavailable
/home/eligence/nodevenv/daily-app.eligence.dev/24/bin/node: fork: Resource temporarily unavailable
/home/eligence/nodevenv/daily-app.eligence.dev/24/bin/node: fork: retry: Resource temporarily unavailable
/home/eligence/nodevenv/daily-app.eligence.dev/24/bin/node: fork: retry: Resource temporarily unavailable
/home/eligence/nodevenv/daily-app.eligence.dev/24/bin/node: fork: retry: Resource temporarily unavailable
/home/eligence/nodevenv/daily-app.eligence.dev/24/bin/node: fork: retry: Resource temporarily unavailable
/home/eligence/nodevenv/daily-app.eligence.dev/24/bin/node: fork: Resource temporarily unavailable
/home/eligence/nodevenv/daily-app.eligence.dev/24/bin/node: fork: retry: Resource temporarily unavailable
/home/eligence/nodevenv/daily-app.eligence.dev/24/bin/node: fork: retry: Resource temporarily unavailable
/home/eligence/nodevenv/daily-app.eligence.dev/24/bin/node: fork: retry: Resource temporarily unavailable
/home/eligence/nodevenv/daily-app.eligence.dev/24/bin/node: fork: retry: Resource temporarily unavailable
/home/eligence/nodevenv/daily-app.eligence.dev/24/bin/node: fork: Resource temporarily unavailable
/home/eligence/nodevenv/daily-app.eligence.dev/24/bin/node: fork: retry: Resource temporarily unavailable
/home/eligence/nodevenv/daily-app.eligence.dev/24/bin/node: fork: retry: Resource temporarily unavailable
/home/eligence/nodevenv/daily-app.eligence.dev/24/bin/node: fork: retry: Resource temporarily unavailable
/home/eligence/nodevenv/daily-app.eligence.dev/24/bin/node: fork: retry: Resource temporarily unavailable
/home/eligence/nodevenv/daily-app.eligence.dev/24/bin/node: fork: Resource temporarily unavailable
/home/eligence/nodevenv/daily-app.eligence.dev/24/bin/node: fork: retry: Resource temporarily unavailable
/home/eligence/nodevenv/daily-app.eligence.dev/24/bin/node: fork: retry: Resource temporarily unavailable
/home/eligence/nodevenv/daily-app.eligence.dev/24/bin/node: fork: retry: Resource temporarily unavailable
/home/eligence/nodevenv/daily-app.eligence.dev/24/bin/node: fork: retry: Resource temporarily unavailable
/home/eligence/nodevenv/daily-app.eligence.dev/24/bin/node: fork: Resource temporarily unavailable
/home/eligence/nodevenv/daily-app.eligence.dev/24/bin/node: fork: retry: Resource temporarily unavailable
/home/eligence/nodevenv/daily-app.eligence.dev/24/bin/node: fork: retry: Resource temporarily unavailable
/home/eligence/nodevenv/daily-app.eligence.dev/24/bin/node: fork: retry: Resource temporarily unavailable
/home/eligence/nodevenv/daily-app.eligence.dev/24/bin/node: fork: retry: Resource temporarily unavailable
/home/eligence/nodevenv/daily-app.eligence.dev/24/bin/node: fork: Resource temporarily unavailable
/home/eligence/nodevenv/daily-app.eligence.dev/24/bin/node: fork: retry: Resource temporarily unavailable
/home/eligence/nodevenv/daily-app.eligence.dev/24/bin/node: fork: retry: Resource temporarily unavailable
/home/eligence/nodevenv/daily-app.eligence.dev/24/bin/node: fork: retry: Resource temporarily unavailable
/home/eligence/nodevenv/daily-app.eligence.dev/24/bin/node: fork: retry: Resource temporarily unavailable
/home/eligence/nodevenv/daily-app.eligence.dev/24/bin/node: fork: Resource temporarily unavailable
/home/eligence/nodevenv/daily-app.eligence.dev/24/bin/node: fork: retry: Resource temporarily unavailable
/home/eligence/nodevenv/daily-app.eligence.dev/24/bin/node: fork: retry: Resource temporarily unavailable
/home/eligence/nodevenv/daily-app.eligence.dev/24/bin/node: fork: retry: Resource temporarily unavailable
/home/eligence/nodevenv/daily-app.eligence.dev/24/bin/node: fork: retry: Resource temporarily unavailable
/home/eligence/nodevenv/daily-app.eligence.dev/24/bin/node: fork: Resource temporarily unavailable
/home/eligence/nodevenv/daily-app.eligence.dev/24/bin/node: fork: retry: Resource temporarily unavailable
/home/eligence/nodevenv/daily-app.eligence.dev/24/bin/node: fork: retry: Resource temporarily unavailable
/home/eligence/nodevenv/daily-app.eligence.dev/24/bin/node: fork: retry: Resource temporarily unavailable
/home/eligence/nodevenv/daily-app.eligence.dev/24/bin/node: fork: retry: Resource temporarily unavailable
/home/eligence/nodevenv/daily-app.eligence.dev/24/bin/node: fork: Resource temporarily unavailable
/home/eligence/nodevenv/daily-app.eligence.dev/24/bin/node: fork: retry: Resource temporarily unavailable
/home/eligence/nodevenv/daily-app.eligence.dev/24/bin/node: fork: retry: Resource temporarily unavailable
/home/eligence/nodevenv/daily-app.eligence.dev/24/bin/node: fork: retry: Resource temporarily unavailable
/home/eligence/nodevenv/daily-app.eligence.dev/24/bin/node: fork: retry: Resource temporarily unavailable
/home/eligence/nodevenv/daily-app.eligence.dev/24/bin/node: fork: Resource temporarily unavailable
/home/eligence/nodevenv/daily-app.eligence.dev/24/bin/node: fork: retry: Resource temporarily unavailable
/home/eligence/nodevenv/daily-app.eligence.dev/24/bin/node: fork: retry: Resource temporarily unavailable
/home/eligence/nodevenv/daily-app.eligence.dev/24/bin/node: fork: retry: Resource temporarily unavailable
/home/eligence/nodevenv/daily-app.eligence.dev/24/bin/node: fork: retry: Resource temporarily unavailable
/home/eligence/nodevenv/daily-app.eligence.dev/24/bin/node: fork: Resource temporarily unavailable
/home/eligence/nodevenv/daily-app.eligence.dev/24/bin/node: fork: retry: Resource temporarily unavailable
/home/eligence/nodevenv/daily-app.eligence.dev/24/bin/node: fork: retry: Resource temporarily unavailable
/home/eligence/nodevenv/daily-app.eligence.dev/24/bin/node: fork: retry: Resource temporarily unavailable
/home/eligence/nodevenv/daily-app.eligence.dev/24/bin/node: fork: retry: Resource temporarily unavailable
/home/eligence/nodevenv/daily-app.eligence.dev/24/bin/node: fork: Resource temporarily unavailable
/home/eligence/nodevenv/daily-app.eligence.dev/24/bin/node: fork: retry: Resource temporarily unavailable
/home/eligence/nodevenv/daily-app.eligence.dev/24/bin/node: fork: retry: Resource temporarily unavailable
/home/eligence/nodevenv/daily-app.eligence.dev/24/bin/node: fork: retry: Resource temporarily unavailable
/home/eligence/nodevenv/daily-app.eligence.dev/24/bin/node: fork: retry: Resource temporarily unavailable
/home/eligence/nodevenv/daily-app.eligence.dev/24/bin/node: fork: Resource temporarily unavailable
/home/eligence/nodevenv/daily-app.eligence.dev/24/bin/node: fork: retry: Resource temporarily unavailable
/home/eligence/nodevenv/daily-app.eligence.dev/24/bin/node: fork: retry: Resource temporarily unavailable
/home/eligence/nodevenv/daily-app.eligence.dev/24/bin/node: fork: retry: Resource temporarily unavailable
/home/eligence/nodevenv/daily-app.eligence.dev/24/bin/node: fork: retry: Resource temporarily unavailable
/home/eligence/nodevenv/daily-app.eligence.dev/24/bin/node: fork: Resource temporarily unavailable
/home/eligence/nodevenv/daily-app.eligence.dev/24/bin/node: fork: retry: Resource temporarily unavailable
/home/eligence/nodevenv/daily-app.eligence.dev/24/bin/node: fork: retry: Resource temporarily unavailable
/home/eligence/nodevenv/daily-app.eligence.dev/24/bin/node: fork: retry: Resource temporarily unavailable
/home/eligence/nodevenv/daily-app.eligence.dev/24/bin/node: fork: retry: Resource temporarily unavailable
/home/eligence/nodevenv/daily-app.eligence.dev/24/bin/node: fork: Resource temporarily unavailable
/home/eligence/nodevenv/daily-app.eligence.dev/24/bin/node: fork: retry: Resource temporarily unavailable
/home/eligence/nodevenv/daily-app.eligence.dev/24/bin/node: fork: retry: Resource temporarily unavailable
/home/eligence/nodevenv/daily-app.eligence.dev/24/bin/node: fork: retry: Resource temporarily unavailable
/home/eligence/nodevenv/daily-app.eligence.dev/24/bin/node: fork: retry: Resource temporarily unavailable
/home/eligence/nodevenv/daily-app.eligence.dev/24/bin/node: fork: Resource temporarily unavailable
/home/eligence/nodevenv/daily-app.eligence.dev/24/bin/node: fork: retry: Resource temporarily unavailable
/home/eligence/nodevenv/daily-app.eligence.dev/24/bin/node: fork: retry: Resource temporarily unavailable
/home/eligence/nodevenv/daily-app.eligence.dev/24/bin/node: fork: retry: Resource temporarily unavailable
/home/eligence/nodevenv/daily-app.eligence.dev/24/bin/node: fork: retry: Resource temporarily unavailable
/home/eligence/nodevenv/daily-app.eligence.dev/24/bin/node: fork: Resource temporarily unavailable
/home/eligence/nodevenv/daily-app.eligence.dev/24/bin/node: fork: retry: Resource temporarily unavailable
/home/eligence/nodevenv/daily-app.eligence.dev/24/bin/node: fork: retry: Resource temporarily unavailable
/home/eligence/nodevenv/daily-app.eligence.dev/24/bin/node: fork: retry: Resource temporarily unavailable
/home/eligence/nodevenv/daily-app.eligence.dev/24/bin/node: fork: retry: Resource temporarily unavailable
/home/eligence/nodevenv/daily-app.eligence.dev/24/bin/node: fork: Resource temporarily unavailable
/home/eligence/nodevenv/daily-app.eligence.dev/24/bin/node: fork: retry: Resource temporarily unavailable
/home/eligence/nodevenv/daily-app.eligence.dev/24/bin/node: fork: retry: Resource temporarily unavailable
/home/eligence/nodevenv/daily-app.eligence.dev/24/bin/node: fork: retry: Resource temporarily unavailable
/home/eligence/nodevenv/daily-app.eligence.dev/24/bin/node: fork: retry: Resource temporarily unavailable
/home/eligence/nodevenv/daily-app.eligence.dev/24/bin/node: fork: Resource temporarily unavailable
/home/eligence/nodevenv/daily-app.eligence.dev/24/bin/node: fork: retry: Resource temporarily unavailable
/home/eligence/nodevenv/daily-app.eligence.dev/24/bin/node: fork: retry: Resource temporarily unavailable
/home/eligence/nodevenv/daily-app.eligence.dev/24/bin/node: fork: retry: Resource temporarily unavailable
/home/eligence/nodevenv/daily-app.eligence.dev/24/bin/node: fork: retry: Resource temporarily unavailable
/home/eligence/nodevenv/daily-app.eligence.dev/24/bin/node: fork: Resource temporarily unavailable
/home/eligence/nodevenv/daily-app.eligence.dev/24/bin/node: fork: retry: Resource temporarily unavailable
/home/eligence/nodevenv/daily-app.eligence.dev/24/bin/node: fork: retry: Resource temporarily unavailable
/home/eligence/nodevenv/daily-app.eligence.dev/24/bin/node: fork: retry: Resource temporarily unavailable
/home/eligence/nodevenv/daily-app.eligence.dev/24/bin/node: fork: retry: Resource temporarily unavailable
/home/eligence/nodevenv/daily-app.eligence.dev/24/bin/node: fork: Resource temporarily unavailable
/home/eligence/nodevenv/daily-app.eligence.dev/24/bin/node: fork: retry: Resource temporarily unavailable
/home/eligence/nodevenv/daily-app.eligence.dev/24/bin/node: fork: retry: Resource temporarily unavailable
/home/eligence/nodevenv/daily-app.eligence.dev/24/bin/node: fork: retry: Resource temporarily unavailable
/home/eligence/nodevenv/daily-app.eligence.dev/24/bin/node: fork: retry: Resource temporarily unavailable
/home/eligence/nodevenv/daily-app.eligence.dev/24/bin/node: fork: Resource temporarily unavailable
(node:1616758) [DEP0169] DeprecationWarning: `url.parse()` behavior is not standardized and prone to errors that have security implications. Use the WHATWG URL API instead. CVEs are not issued for `url.parse()` vulnerabilities.
(Use `node --trace-deprecation ...` to show where the warning was created)
/home/eligence/nodevenv/daily-app.eligence.dev/24/bin/node: fork: retry: Resource temporarily unavailable
/home/eligence/nodevenv/daily-app.eligence.dev/24/bin/node: fork: retry: Resource temporarily unavailable
/home/eligence/nodevenv/daily-app.eligence.dev/24/bin/node: fork: retry: Resource temporarily unavailable
/home/eligence/nodevenv/daily-app.eligence.dev/24/bin/node: fork: retry: Resource temporarily unavailable
/home/eligence/nodevenv/daily-app.eligence.dev/24/bin/node: fork: Resource temporarily unavailable
/home/eligence/nodevenv/daily-app.eligence.dev/24/bin/node: fork: retry: Resource temporarily unavailable
/home/eligence/nodevenv/daily-app.eligence.dev/24/bin/node: fork: retry: Resource temporarily unavailable
/home/eligence/nodevenv/daily-app.eligence.dev/24/bin/node: fork: retry: Resource temporarily unavailable
/home/eligence/nodevenv/daily-app.eligence.dev/24/bin/node: fork: retry: Resource temporarily unavailable
/home/eligence/nodevenv/daily-app.eligence.dev/24/bin/node: fork: Resource temporarily unavailable
/home/eligence/nodevenv/daily-app.eligence.dev/24/bin/node: fork: retry: Resource temporarily unavailable
/home/eligence/nodevenv/daily-app.eligence.dev/24/bin/node: fork: retry: Resource temporarily unavailable
/home/eligence/nodevenv/daily-app.eligence.dev/24/bin/node: fork: retry: Resource temporarily unavailable
/home/eligence/nodevenv/daily-app.eligence.dev/24/bin/node: fork: retry: Resource temporarily unavailable
/home/eligence/nodevenv/daily-app.eligence.dev/24/bin/node: fork: Resource temporarily unavailable
/home/eligence/nodevenv/daily-app.eligence.dev/24/bin/node: fork: retry: Resource temporarily unavailable
/home/eligence/nodevenv/daily-app.eligence.dev/24/bin/node: fork: retry: Resource temporarily unavailable
/home/eligence/nodevenv/daily-app.eligence.dev/24/bin/node: fork: retry: Resource temporarily unavailable
/home/eligence/nodevenv/daily-app.eligence.dev/24/bin/node: fork: retry: Resource temporarily unavailable
/home/eligence/nodevenv/daily-app.eligence.dev/24/bin/node: fork: Resource temporarily unavailable
(node:1658643) [DEP0169] DeprecationWarning: `url.parse()` behavior is not standardized and prone to errors that have security implications. Use the WHATWG URL API instead. CVEs are not issued for `url.parse()` vulnerabilities.
(Use `node --trace-deprecation ...` to show where the warning was created)
(node:1665142) [DEP0169] DeprecationWarning: `url.parse()` behavior is not standardized and prone to errors that have security implications. Use the WHATWG URL API instead. CVEs are not issued for `url.parse()` vulnerabilities.
(Use `node --trace-deprecation ...` to show where the warning was created)
(node:1716104) [DEP0169] DeprecationWarning: `url.parse()` behavior is not standardized and prone to errors that have security implications. Use the WHATWG URL API instead. CVEs are not issued for `url.parse()` vulnerabilities.
(Use `node --trace-deprecation ...` to show where the warning was created)
(node:1814970) [DEP0169] DeprecationWarning: `url.parse()` behavior is not standardized and prone to errors that have security implications. Use the WHATWG URL API instead. CVEs are not issued for `url.parse()` vulnerabilities.
(Use `node --trace-deprecation ...` to show where the warning was created)
⨯ Error [PrismaClientKnownRequestError]: 
Invalid `prisma.kid.findUnique()` invocation:


Can't reach database server at `localhost:3306`

Please make sure your database server is running at `localhost:3306`.
    at async j (.next/server/app/kid/[loginToken]/page.js:1:6428) {
  code: 'P1001',
  meta: { modelName: 'Kid', database_location: 'localhost:3306' },
  clientVersion: '6.19.3',
  digest: '2575608612'
}
⨯ Error [PrismaClientKnownRequestError]: 
Invalid `prisma.kid.findUnique()` invocation:


Can't reach database server at `localhost:3306`

Please make sure your database server is running at `localhost:3306`.
    at async j (.next/server/app/kid/[loginToken]/page.js:1:6428) {
  code: 'P1001',
  meta: { modelName: 'Kid', database_location: 'localhost:3306' },
  clientVersion: '6.19.3',
  digest: '2575608612'
}
⨯ Error [PrismaClientKnownRequestError]: 
Invalid `prisma.kid.findUnique()` invocation:


Can't reach database server at `localhost:3306`

Please make sure your database server is running at `localhost:3306`.
    at async j (.next/server/app/kid/[loginToken]/page.js:1:6428) {
  code: 'P1001',
  meta: { modelName: 'Kid', database_location: 'localhost:3306' },
  clientVersion: '6.19.3',
  digest: '2575608612'
}
⨯ Error [PrismaClientKnownRequestError]: 
Invalid `prisma.user.findUnique()` invocation:


Can't reach database server at `localhost:3306`

Please make sure your database server is running at `localhost:3306`.
    at async n (.next/server/app/parent/page.js:1:7076)
    at async k (.next/server/app/parent/page.js:2:51095) {
  code: 'P1001',
  meta: { modelName: 'User', database_location: 'localhost:3306' },
  clientVersion: '6.19.3',
  digest: '2567540260'
}
⨯ Error [PrismaClientKnownRequestError]: 
Invalid `prisma.kid.findUnique()` invocation:


Can't reach database server at `localhost:3306`

Please make sure your database server is running at `localhost:3306`.
    at async j (.next/server/app/kid/[loginToken]/page.js:1:6428) {
  code: 'P1001',
  meta: { modelName: 'Kid', database_location: 'localhost:3306' },
  clientVersion: '6.19.3',
  digest: '2575608612'
}
⨯ Error [PrismaClientKnownRequestError]: 
Invalid `prisma.kid.findUnique()` invocation:


Can't reach database server at `localhost:3306`

Please make sure your database server is running at `localhost:3306`.
    at async j (.next/server/app/kid/[loginToken]/page.js:1:6428) {
  code: 'P1001',
  meta: { modelName: 'Kid', database_location: 'localhost:3306' },
  clientVersion: '6.19.3',
  digest: '2575608612'
}
⨯ Error [PrismaClientKnownRequestError]: 
Invalid `prisma.kid.findUnique()` invocation:


Can't reach database server at `localhost:3306`

Please make sure your database server is running at `localhost:3306`.
    at async j (.next/server/app/kid/[loginToken]/page.js:1:6428) {
  code: 'P1001',
  meta: { modelName: 'Kid', database_location: 'localhost:3306' },
  clientVersion: '6.19.3',
  digest: '2575608612'
}
⨯ Error [PrismaClientKnownRequestError]: 
Invalid `prisma.kid.findUnique()` invocation:


Can't reach database server at `localhost:3306`

Please make sure your database server is running at `localhost:3306`.
    at async j (.next/server/app/kid/[loginToken]/page.js:1:6428) {
  code: 'P1001',
  meta: { modelName: 'Kid', database_location: 'localhost:3306' },
  clientVersion: '6.19.3',
  digest: '2575608612'
}
⨯ Error [PrismaClientKnownRequestError]: 
Invalid `prisma.kid.findUnique()` invocation:


Can't reach database server at `localhost:3306`

Please make sure your database server is running at `localhost:3306`.
    at async j (.next/server/app/kid/[loginToken]/page.js:1:6428) {
  code: 'P1001',
  meta: { modelName: 'Kid', database_location: 'localhost:3306' },
  clientVersion: '6.19.3',
  digest: '2575608612'
}