Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Unhandled websocket error during Muse connectivity #61

Open
jdpigeon opened this issue Feb 24, 2019 · 0 comments
Open

Unhandled websocket error during Muse connectivity #61

jdpigeon opened this issue Feb 24, 2019 · 0 comments
Labels
bug Something isn't working

Comments

@jdpigeon
Copy link
Contributor

jdpigeon commented Feb 24, 2019 •
edited
Loading

Muse doesn't power down, and connectivity appears to be maintained if navigating back to collection screen

Error: connect ETIMEDOUT 14.160.32.18:54321
    at Object._errnoException (util.js:1024)
    at _exceptionWithHostPort (util.js:1046)
    at TCPConnectWrap.afterConnect [as oncomplete] (net.js:1182)
_errnoException @ util.js:1024
_exceptionWithHostPort @ util.js:1046
afterConnect @ net.js:1182
websocket.js:531 Uncaught TypeError: Cannot read property 'aborted' of null
@jdpigeon jdpigeon added the bug Something isn't working label Feb 24, 2019
@jdpigeon jdpigeon changed the title Unhandled websocket error when Muse moves too far away from computer Unhandled websocket errorduring Muse connectivity Feb 25, 2019
@jdpigeon jdpigeon changed the title Unhandled websocket errorduring Muse connectivity Unhandled websocket error during Muse connectivity Feb 25, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
bug Something isn't working
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@jdpigeon