-
Notifications
You must be signed in to change notification settings - Fork 1
Open
Description
When trying to connect to an ose-example-rpi instance from freshly started Firefox on Android, the backend crashes with the following console output. When connecting to the restarted backend without restarting Firefox, the problem doesn't appear.
rpi> 1444070232 'NOTICE | ose | CLI script finished.'
rpi> 1444070254 'NOTICE | ose | Client socket connected, authenticating ... |' '/69ba438d'
TX >>>>>> undefined {"space":"example.org","peer":"rpi"}
rpi> TX >>>>>> e340ef9b {"confirmed":true}
1444070255 'NOTICE | ose | Connected. |' { space: 'example.org', peer: 'e340ef9b', url: undefined }
RX <<<<<< e340ef9b {"type":"space","newLid":4013565285,"space":"example.org"}
TX >>>>>> e340ef9b {"type":"open","lid":4013565285,"data":{"home":false}}
========================================================
1444070277 'ERROR | ose | undefined |' 'false == true'
Stack Trace:
AssertionError: false == true
at ServerResponse.resOnFinish (_http_server.js:474:7)
at emitNone (events.js:67:13)
at ServerResponse.emit (events.js:166:7)
at finish (_http_outgoing.js:529:10)
at doNTCallback0 (node.js:407:9)
at process._tickCallback (node.js:336:13)
--------------------------------------------------------
Logged at:
Trace
at Object.exports.error.exports.err (/home/ose/ose-example-rpi/node_modules/ose/lib/logger.js:276:11)
at process.onError (/home/ose/ose-example-rpi/node_modules/ose/lib/node.js:98:9)
at emitOne (events.js:77:13)
at process.emit (events.js:169:7)
at process._fatalException (node.js:211:26)
========================================================
TX >>>>>> e340ef9b {"type":"close","lid":4013565285,"data":"remove"}
1444070277 'DEBUG | ose | State patched |' '{"entry":"heater1","state":{"enabled":false}}'
1444070277 'NOTICE | ose | Peer closed |' { peer: 'e340ef9b' }
Reactions are currently unavailable