You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi, firstly, thanks for an awesome plugin/framework, really enjoying it.
We have recently deployed our first application with vike to production, and get this error thrown sometimes.
Every time, it is paired with error logs before and after that the backend service we are calling either times out or returns 503 service unavailable, so I think it's related to that, just in some cases, we get this error from vike instead.
We fetch data from this api in the onBeforeRender hook in index.page.server.tsx (haven't upgraded to v1 just yet), and that service sometimes has issues (slow, memory issues). That team is looking into upgrading the memory on their side but for now I'm curious on why we get these errors on some requests.
Error: [vike@0.4.160][Bug]YoustumbleduponaVikebug.Gotohttps://github.com/vikejs/vike/issues/new and copy-paste this error. A maintainer will fix the bug (usually under 24 hours).atextractFromPath(file:///home/site/wwwroot/node_modules/.pnpm/[email protected][email protected]/node_modules/vike/dist/esm/node/runtime/renderPage/logHintForCjsEsmError.js:228:5)atextractFromNodeModulesPath(file:///home/site/wwwroot/node_modules/.pnpm/[email protected][email protected]/node_modules/vike/dist/esm/node/runtime/renderPage/logHintForCjsEsmError.js:244:25)atgetPackageName_stack1(file:///home/site/wwwroot/node_modules/.pnpm/[email protected][email protected]/node_modules/vike/dist/esm/node/runtime/renderPage/logHintForCjsEsmError.js:192:12)atisCjsEsmError(file:///home/site/wwwroot/node_modules/.pnpm/[email protected][email protected]/node_modules/vike/dist/esm/node/runtime/renderPage/logHintForCjsEsmError.js:52:32)atgetHint(file:///home/site/wwwroot/node_modules/.pnpm/[email protected][email protected]/node_modules/vike/dist/esm/node/runtime/renderPage/logHintForCjsEsmError.js:21:17)atlogHintForCjsEsmError(file:///home/site/wwwroot/node_modules/.pnpm/[email protected][email protected]/node_modules/vike/dist/esm/node/runtime/renderPage/logHintForCjsEsmError.js:12:18)atonRuntimeError(file:///home/site/wwwroot/node_modules/.pnpm/[email protected][email protected]/node_modules/vike/dist/esm/node/runtime/renderPage/loggerProd.js:24:5)atlogErrorProd(file:///home/site/wwwroot/node_modules/.pnpm/[email protected][email protected]/node_modules/vike/dist/esm/node/runtime/renderPage/loggerProd.js:19:5)atrenderPageAlreadyPrepared(file:///home/site/wwwroot/node_modules/.pnpm/[email protected][email protected]/node_modules/vike/dist/esm/node/runtime/renderPage.js:126:13)atasyncrenderPageAndPrepare(file:///home/site/wwwroot/node_modules/.pnpm/[email protected][email protected]/node_modules/vike/dist/esm/node/runtime/renderPage.js:101:12)atasyncrenderPage_wrapper(file:///home/site/wwwroot/node_modules/.pnpm/[email protected][email protected]/node_modules/vike/dist/esm/node/runtime/renderPage.js:26:24)atasyncrenderPage(file:///home/site/wwwroot/node_modules/.pnpm/[email protected][email protected]/node_modules/vike/dist/esm/node/runtime/renderPage.js:46:50)atasynchandleRenderReactApp(file:///home/site/wwwroot/dist/server.mjs:1456:23)
The text was updated successfully, but these errors were encountered:
Description
Hi, firstly, thanks for an awesome plugin/framework, really enjoying it.
We have recently deployed our first application with vike to production, and get this error thrown sometimes.
Every time, it is paired with error logs before and after that the backend service we are calling either times out or returns 503 service unavailable, so I think it's related to that, just in some cases, we get this error from vike instead.
We fetch data from this api in the
onBeforeRender
hook inindex.page.server.tsx
(haven't upgraded to v1 just yet), and that service sometimes has issues (slow, memory issues). That team is looking into upgrading the memory on their side but for now I'm curious on why we get these errors on some requests.The text was updated successfully, but these errors were encountered: