-
Notifications
You must be signed in to change notification settings - Fork 10.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
SSR Function crashing from deployed Workspace App #38986
Comments
Not sure what the policy is re. commenting, or if the gatsby/packages/gatsby/src/utils/page-ssr-module/lambda.ts Lines 34 to 35 in 9584173
Because when I check the output of the Function in May 22, 08:45:25 AM: ba81e0e6 2024-05-22T07:45:26.352Z undefined INFO Preparing Gatsby filesystem {May 22, 08:45:25 AM: ba81e0e6 from: '/var/task/.cache',
May 22, 08:45:25 AM: ba81e0e6 to: '/tmp/gatsby/.cache',
May 22, 08:45:25 AM: ba81e0e6 rewrites: [
May 22, 08:45:25 AM: ba81e0e6 [ '/var/task/.cache/caches', '/tmp/gatsby/.cache/caches' ],
May 22, 08:45:25 AM: ba81e0e6 [
May 22, 08:45:25 AM: ba81e0e6 '/var/task/.cache/caches-lmdb',
May 22, 08:45:25 AM: ba81e0e6 '/tmp/gatsby/.cache/caches-lmdb'
May 22, 08:45:25 AM: ba81e0e6 ],
May 22, 08:45:25 AM: ba81e0e6 [ '/var/task/.cache/data', '/tmp/gatsby/.cache/data' ]
May 22, 08:45:25 AM: ba81e0e6 ]
May 22, 08:45:25 AM: ba81e0e6 } So it seems like that |
Looks like #39005 might fix this? |
Preliminary Checks
Description
I think there's a problem when deploying a SSR
gatsby
app from ayarn workspace
app, deployed tonetlify
: when deployed tonetlify
, the SSR engine crashes on initial invocation. here's the stacktrace:From what I can interpret in the stacktrace, the problem may be that
/var/task/.cache/data
is not found as the path is incorrect in that execution scope; I think it should be/var/task/apps/gatsby-test/.cache/data
(seesetupFsWrapper
in the trace).The SSR engine initialised fine in the supplied repo, when the
gatsby
instance was in the root of the repo ... however, in moving it into ayarn workspace
context, the above problem then appears. So It seems likegatsby
's SSR engine expects a "root" path throughout? Hopefully it's clear & the answer simple as the inability to deploy agatsby
site within workspaces is a problem ...Reproduction Link
https://github.com/amaccann/gatsby-renofi-test
Steps to Reproduce
netlify
app using the ☝️ example repo.netlify
Site & set Deploy settings to deploy; see below for the settings used in the failing context....
Expected Result
Site should render fine, specifically the paths using SSR engine's output (in this case, a simple public GQL I have access to)
Actual Result
When visting the deploy URL, the URL should simply report
Invocation failed
and a crash stacktrace as below ...Environment
The text was updated successfully, but these errors were encountered: