https://serverless-stack.com/ logo
Join Slack
Powered by
When running locally, is this to be expected? ```U...
# help
g
When running locally, is this to be expected?
Copy code
Unexpected Top Level Error: Error: socket hang up
t
I don't think so, can you show more of the log? And does this cause any issues?
g
I am running deploy now to see if it fixes it
t
are you seeing this error on a function invocation?
g
the error seems to happen only if I "ignore" it for about 20 minutes or more
While I am actively changing code and checking back with the browser, all is good. If I switch to a different task or leave to grab a bite to eat, I come back to that message.
t
ah interesting
This might be a side effect of something else I'm fixing soon
g
cool. Thanks for the reply
That deploy fixed it
t
restarting 
sst start
didn't fix it?
g
nope
had to
Copy code
sst deploy
first
t
Is it possible you and your coworker are using the same stage name and he connected to it?
g
no
he is on vacation
and
npx start still isn't working
All I get when I use npx start is the SST splash screen
That wasn't the case before this happened. But it's the case now
t
When the stage is running under 
sst start
we do not deploy the frontend. This is because for local development people likely want to run the frontend locally for instant reloads
g
in my terminal window, it looks like it is working. But when I go to the browser, I see the splash screen
Copy code
Stack glm-serverless-app-frontend
  Status: no changes
  Outputs:
    SiteUrl: <https://d3sp3ytfkg9bsz.cloudfront.net>
  ReactSite:
    REACT_APP_API_URL: <https://rdo2dbm2f0.execute-api.us-east-2.amazonaws.com>
    REACT_APP_BUCKET: glm-serverless-app-storage-uploadsbucketc4b27cc7-1u9zui7gztt5p
    REACT_APP_IDENTITY_POOL_ID: us-east-2:7b3507d1-124e-44c5-8b7d-c98443ccaa63
    REACT_APP_REGION: us-east-2
    REACT_APP_USER_POOL_CLIENT_ID: 3e44avrp5heacuun7athghrfks
    REACT_APP_USER_POOL_ID: us-east-2_zBBYt6WQj


==========================
 Starting Live Lambda Dev
==========================

Transpiling Lambda code...
Debug session started. Listening for requests
t
So we deploy a placeholder side - we're actually fixing the copy on it right now to make that more clear
g
So, in that case, what URL do I use?
t
You would have to go into your frontend folder and do 
npm start
or something to bring it up locally
g
gotcha
so that's when it's running the frontend stuff locally, but proxying the lambda with the sst magic dust, right?
This is just very cool stuff.
t
Yep exactly!
Open in Slack
PreviousNext
Powered by