Nick Gauthier

I am not sure how a websocket endpoint is supposed to behave when a non-websocket connection comes in. Does it behave properly when you make a normal JS websocket connection?

Are you sure you're calling the close, and that it is the only socket open? Also, please log when the socket opens, because maybe the websocket is re-establishing the connection...

I'm not sure. It looks ok to me. On Tue, Mar 11, 2014 at 3:57 PM, tyrbo [email protected] wrote: > Problem solved when using the latest from github. > New...

Hm, that would be tricky. Perhaps in an integration test (a.k.a. request spec or acceptance spec) it's possible to access the rack test driver's socket from capybara? Or perhaps we...

hmm, probably just reload your browser (and any tabs open)? I don't think I saw this happen to me when developing.

I'm not really sure. I didn't see this while working on my project. Does it happen if you run the example project? https://github.com/ngauthier/sock-chat Nick

Is there any difference at all between your folder and the example? I would expect the Gemfile.lock to be a little different because of jruby. Anything else?

Hm, interesting point. The `!` really just means "it will throw an exception" but I totally understand how Capybara wait behavior can be confusing. IMO the main workaround would be...

Yup. Would be nice if `find_by!` was more capybara-like.

Capybara used to expose a wait function but too many people used it so they removed it 😄 On Apr 22, 2015 4:26 AM, "Tim Fischbach" [email protected] wrote: > This...