maybe some kind of buffer when reading from the sp...
# sstt
thdxr
03/27/2021, 9:56 PMmaybe some kind of buffer when reading from the spawned node proc or max websocket frame size?
j
Jay
03/27/2021, 10:22 PM
Yeah we might not be handling this. Does the log in the
.buildf
Frank
03/28/2021, 2:43 AM
@thdxr APIG websocket has a 32KB frame size limit.. maybe that’s the culprit.
Frank
03/28/2021, 2:48 AM
Can you send me ur
.build/sst-debug.logFrank
03/28/2021, 2:49 AM
U might want to redact sensitive info in the debug log. (ie. Lambda IAM credentials and sensitive environment variables)
t
thdxr
04/09/2021, 4:13 AM Copy code
[2021-04-09T00:12:09.801] [DEBUG] websocket - Websocket connection closed { code: 1009, reason: 'Message too big' }thdxr
04/09/2021, 4:13 AMyep that's it
f
Frank
04/09/2021, 8:11 AM
Got it! Will take a look at it tmr.
Frank
04/09/2021, 8:12 AM
Thanks for looking into this!
Frank
04/14/2021, 10:06 AM
@thdxr Fixed in v0.10.11. For large websocket payloads, SST will now send them in 120KB chunks (APIG limit is 128KB), and the receiver pieces it back together.
t
thdxr
04/14/2021, 12:56 PMAmazing thank you!