You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Your .setTimeout method does not work correctly - when calling .setTimeout the "timeout" event is only called once
Also your .setTimeout only takes write activity into account
The NodeJS implementation however states "timeout" should be called after ms of any inactivity
Steps to reproduce
Steps to reproduce the behavior:
Create TCP Server
Create TCP connection
Call .setTimeout(3000)
Don`t send anything
Received "timeout" after 3000ms as expected
Send something(timeout is not reset)
Wait another 3000ms --> No "timeout" event will be received
Hi,I ll take some time because I m very busy atmThat is why I added the fix diff into the issue, maybe someone gets to it faster than I will but I will try to make it happenOn Jun 19, 2024 14:44, Rodrigo Martín ***@***.***> wrote:
@Fabian-Lobnig, thanks for the feedback! Could you create a PR with your fix?
—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you were mentioned.Message ID: ***@***.***>
Description
Your .setTimeout method does not work correctly - when calling .setTimeout the "timeout" event is only called once
Also your .setTimeout only takes write activity into account
The NodeJS implementation however states "timeout" should be called after ms of any inactivity
Steps to reproduce
Steps to reproduce the behavior:
Fix
Expected
Receive "timeout" event after ms of any inactivity
Relevant information
| OS | any - this is js code |
| react-native-tcp-socket | 6.0.6 |
The text was updated successfully, but these errors were encountered: