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

Handle restarting servers #183

Open
SevereOverfl0w opened this issue May 12, 2019 · 0 comments

Comments

Projects
None yet
1 participant
@SevereOverfl0w
Copy link

commented May 12, 2019

I'm running figwheel via it's API in a system.

Due to automating the (cljs-repl) step for pending-cljs in emacs, and running (go) in another thread (users do this without thinking) it's possible that figwheel-repl will find a nil server, even though one is about to appear.

The exact sequence of events is:

Cljs-thread Clj-thread
(halt)
(init)
(halt)
(cljs-repl)
(start-default-server)
(init) => exception

I added a workaround of (binding [figwheel.repl/*server* true] (cljs-repl)), and it seems to work the majority of the time.

SevereOverfl0w added a commit to juxt/edge that referenced this issue May 12, 2019

Fix figwheel-main starting a server in repl phase
Reference bhauman/figwheel-main#183

If figwheel looks at the server and it has been stopped, it will attempt
to start a server for you.
This causes port conflicts, as we control the server via the system
outside of this.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.