sst start is crashing with
```TypeError: Cannot re...
# helpm
Mike McCall
03/03/2021, 1:21 PMsst start is crashing with
Copy code
TypeError: Cannot read property 'type' of undefined
at returnLambdaResponse (/Users/mike/shoplifted-apps/auto-tags/node_modules/@serverless-stack/cli/scripts/start.js:1128:24)
at ChildProcess.<anonymous> (/Users/mike/shoplifted-apps/auto-tags/node_modules/@serverless-stack/cli/scripts/start.js:1165:5)
at ChildProcess.emit (events.js:315:20)
at ChildProcess.EventEmitter.emit (domain.js:483:12)
at Process.ChildProcess._handle.onexit (internal/child_process.js:275:12)f
Frank
03/03/2021, 6:36 PM
Hmm.. looking at the stack trace.. it seems invoking local function failed
Frank
03/03/2021, 6:38 PM
I’m going to add more debug logging around that part of the code and then cut a release. And you can give it a try with the new version, and send me the debug log.
p
Pål Brattberg
03/03/2021, 9:50 PMI also have a situation where I get this same problem, for a specific function. I haven't been able to cut it down to a small test yet though
Pål Brattberg
03/03/2021, 10:17 PMSeems like it's more likely to happen with larger return payloads. 10k+ chars seems to do the trick
m
Mike McCall
03/03/2021, 10:56 PM@Frank sorry I missed you earlier. Yeah so it's only failing when using live lambda. "lambdaResponse". Running it deployed it works.
Mike McCall
03/03/2021, 10:57 PM Copy code
if (lambdaResponse.type === "timeout") {
...
}
// lambdaResponse is undefinedMike McCall
03/03/2021, 10:57 PMMore debugging would be cool. That's the hard part!
f
Frank
03/03/2021, 11:34 PM
Yeah what @Pål Brattberg suggested could be the cause. The websocket API in the debug stack has a limit of 32KB per package.
Frank
03/03/2021, 11:35 PM
I will cut a release later today with more debugging
m
Mike McCall
03/03/2021, 11:35 PMInteresting.
Mike McCall
03/03/2021, 11:36 PMSounds good. Thanks again.
f
Frank
03/04/2021, 10:07 AM
@Mike McCall @Pål Brattberg The issue should be fix in v0.9.12 (also added detailed debug messages in case it pops up again)
Frank
03/04/2021, 10:08 AM
To update:
Copy code
$ npm install --save --save-exact @serverless-stack/cli@0.9.12 @serverless-stack/resources@0.9.12Frank
03/04/2021, 10:08 AM
Mike, let me know if this fixes ur issue.
p
Pål Brattberg
03/04/2021, 1:01 PMAwesome! This at least fixes my trouble, thanks @Frank!
m
Mike McCall
03/04/2021, 3:28 PM@Frank thanks, I’ll give it a go shortly!
Mike McCall
03/05/2021, 6:08 AM@Frank this seems to have fixed the issue. Thanks.
f
Frank
03/05/2021, 8:18 AM
Nice!
m
Mike McCall
03/06/2021, 7:45 PMThis is actually still happening for me.
f
Frank
03/06/2021, 7:46 PM
Can you send me the debug log in
.build/sst-debug.logm
Mike McCall
03/06/2021, 7:47 PMyup one sec.
f
Frank
03/06/2021, 7:48 PM
Yup, DM me.
Frank
03/06/2021, 7:49 PM
We need to redact the debug log to remove sensitive info from there.
Frank
03/06/2021, 7:54 PM
Btw, the debug log get cleared out at the beginning of every sst command. So I would need the file before u run
sst start