-
Notifications
You must be signed in to change notification settings - Fork 269
Open
Description
Describe the bug
If I use WebSocket communication in NodeJS application, it directly kills the NodeJS program.
Link to the blitz that caused the error
https://stackblitz.com/~/github.com/samchon/tgrid.example.websocket
https://stackblitz.com/~/github.com/wrtnlabs/autobe-playground-stackblitz
Steps to reproduce
Just go up above link, then you directly experience the bug.
There was not such bug before, but suddenly be happened.
Expected behavior
No problem on WebSocket environment.
Parity with Local
- I have run the project in my local machine and I could not reproduce the issue.
Screenshots
Error: Failed to parse http message
at _0x68db6.execute (https://tgridexamplewebsocket-qaei.w-credentialless-staticblitz.com/blitz.55edb8f4.js:31:1008705)
at socketOnData (node:_http_server:7:8628)
at Socket.emit (node:events:30:11034)
at Socket.emit (node:domain:29:5199)
at addChunk (node:internal/streams/readable:230:3174)
at readableAddChunkPushByteMode (node:internal/streams/readable:230:6158)
at Readable.push (node:internal/streams/readable:230:6192)
at _0x3c9154.onStreamRead (node:internal/stream_base_commons:216:2625)
at Object.emit (https://tgridexamplewebsocket-qaei.w-credentialless-staticblitz.com/blitz.55edb8f4.js:31:545954)
at <anonymous> (https://tgridexamplewebsocket-qaei.w-credentialless-staticblitz.com/blitz.55edb8f4.js:31:547543)Platform
- OS: Windows
- Browser: Chrome / Edge / Every Browsers
Additional context
No response
Metadata
Metadata
Assignees
Labels
No labels