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.

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

[HotLoader] starting WS server (ws://0.0.0.0:8082) - starts many times #17

Open
rafath opened this issue May 3, 2017 · 5 comments
Open

Comments

@rafath
Copy link

rafath commented May 3, 2017

rails: 5.0.1
mac os (rvm, ruby 2.4)
using puma (standard command rails s)
Each time I browse any page, with or without react component, in my log console I'm getting many many entries (about 67)

[HotLoader] starting WS server (ws://0.0.0.0:8082) [HotLoader] starting WS server (ws://0.0.0.0:8082) [HotLoader] starting WS server (ws://0.0.0.0:8082) [HotLoader] starting WS server (ws://0.0.0.0:8082) [HotLoader] opened a connection (ws://0.0.0.0:8082) [HotLoader] starting WS server (ws://0.0.0.0:8082) [HotLoader] starting WS server (ws://0.0.0.0:8082) [HotLoader] starting WS server (ws://0.0.0.0:8082) [HotLoader] starting WS server (ws://0.0.0.0:8082) [HotLoader] starting WS server (ws://0.0.0.0:8082)

What is cause of this?

@rafath
Copy link
Author

rafath commented May 3, 2017

It seems, that for every scss or js file - Im getting each hit, is this normal? (in dev env)

@phillipp
Copy link

@rafath Seems to be not normal. I have the same problem after running the dev server for a while, after a restart, problem is gone. Pretty annoying...

@phillipp
Copy link

@rafath I just realized that a new websocket connection is opened for each JSON XHR request. This might be the cause of the massive number of websockets and subsequent multiple reloading for a single change

@criticerz
Copy link

This is happening to us as well. Here is a screenshot of our logs: https://www.dropbox.com/s/tgcaffdqo208d7c/Screenshot%202017-08-07%2017.33.44.png?dl=0

It has significantly slowed down load times on dev mode.

@criticerz
Copy link

@rafath @phillipp I opened a pull request with the fix that solved this issue for me (#19)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants