Closed rhclayto closed 8 years ago
I've determined that nothing in the adapter inside of io.sockets.on 'connection', (socket) =>
is firing. If I put console.log "hey"
just before that line, I get 'hey' in the logs, but if I put it right after that line, nothing. It seems the connection event is never reaching the code in the server. Any ideas why?
Well, just reporting back. I found the cause of my problem. I have multiple socket.io servers running on different ports. I was connecting to the wrong one! Thanks again for this cool adapter!
Hi,
Thanks for putting this up on GitHub. It looks really interesting.
I am having trouble getting this to work for me. I've got the server started & with hubot debugging turned on I get the following messages on start:
I load the front end page served by Express & in the Chrome Devtools Network view I see that socket.io is connected successfully, sending ping & pong messages between the server & client. When I type /help into the text box & submit it, I see that the message is emitted over the websocket. I get 'User /help' in the log window on that page.
That's where it ends. There is no response from hubot. Nothing is logged. When I check the socket object on the client side, it has the property
connected: true
. Is there anything I'm missing here? Thanks.