Now if I quit espruino and restart it, sockets seems to be remained opened in "TIME_WAIT" state, so the new instance is not able to bind to the port.
This happens both in the latest master branch, and in the the RELEASE_1V99. by the time the "RESET" bug was implemented, this does not happened due to the socket reset. Do you have any information, that is this still a linux-related issue (should I set some tcp reuse flag)? (Currently my tcp_tw_reuse flag was set to 1, but it did not solved my problem)
Espruino is a JavaScript interpreter for low-power Microcontrollers. This site is both a support community for Espruino and a place to share what you are working on.
Now if I quit espruino and restart it, sockets seems to be remained opened in "TIME_WAIT" state, so the new instance is not able to bind to the port.
This happens both in the latest master branch, and in the the RELEASE_1V99. by the time the "RESET" bug was implemented, this does not happened due to the socket reset. Do you have any information, that is this still a linux-related issue (should I set some tcp reuse flag)? (Currently my tcp_tw_reuse flag was set to 1, but it did not solved my problem)