Skip to content

Connection Errors does not seem to be handled correctly (using poor wifi) #262

@johnnyman727

Description

@johnnyman727

Moving this issue over from firmware:

Originally reported by @mikaelhm:

It happend really often for me (during nodeconf) that my tessel script chrashed and I got a

Error: ENOENT Cannot connect to 10.11.83.177
stack traceback:
[T]:src/colony/modules/net.js:109: in function <[T]:src/colony/modules/net.js:121>
I used http to send a get request like this:

http
.get('http://10.11.83.177:8082/ws/remote?text= New Weather Report has arrived it is' + weather, function (res) {
console.log("new weatherReport sent");
})
.on('error', function(e) {
console.log("Got error: " + e.message);
});
I guess it should hit the error handler and not just crash.

Metadata

Metadata

Assignees

Labels

No labels
No labels

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions