-
Notifications
You must be signed in to change notification settings - Fork 20
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
A few dozen small, but rapid, socket exchanges kills CC3K #128
Comments
UPDATE: disregard, I don't think this is particularly relevant. Another potential way to trigger (at least something similar). Server: require('net').createServer(function (sock) {
sock.setNoDelay();
for (var i = 0; i < 25; i += 1) setTimeout(function () {
sock.write(".");
}, i*.1e3);
}).listen(5004, function () {
console.log("listening", this.address().port);
}); Tessel: require('net').connect(5004, "192.168.4.114", function () {
console.log("connected, waiting");
setInterval(function () {
console.log("spin");
var i = 100000;
while (--i) ;
console.log("done");
}, 1e3);
}); There's no timeout errors, but |
Will tessel/t1-runtime#713 improve this situation at least by making it detectable? |
Run this somewhere the Tessel can talk to:
Run this with
tessel run -l all -s script.js
:Gets stuck in a loop like the following, and then needs a power cycle before doing any other WiFi stuff:
Full log at https://gist.github.com/natevw/6c39419e1e3bca9bf17c
The text was updated successfully, but these errors were encountered: