Closed nguyentrannhan closed 2 months ago
I don't understand what the issue is supposed to be here and its attempted fix. If you are sending a malformed payload that cannot be processed, the socket will be closed as intended. What is the "wrong input" you are sending in joinChat
?
Discussed further on the PR here.
Description
When pipeline.ProcessRequest return false, the nakama-js can be timeout because the IncommingLoop is break. To fix it, we add a flag for safely break the IncommingLoop
Steps to Reproduce
Expected Result
nakama-js should return with invalid input error not socket timeout
Actual Result
Error is thrown with socket timeout
Context
Your Environment