josevalim
Most Liked
cvkmohan
soup
Users might want to use --no-pry when running Phoenix in IEx, especially with liveview, or you’ll have processes/events/requests timeout.
iex --sname xyz --cookie abc --no-pry -S mix phx.server
There also seems to be some order dependency on the arguments, so watch out for that:
% iex --no-pry --sname local -S mix phx.server
Erlang/OTP 25 [erts-13.0.4] [source] [64-bit] [smp:4:4] [ds:4:4:10] [async-threads:1] [jit:ns]
--sname : Unknown option
No file named local
muelthe
As always, thank you <3
josevalim
Good catch. Fixed in v1.14 and main branches.
soup
Because IEx.pry suspends execution in the view process so it stops responding to other messages. This can cause the surrounding infrastructure to think the view is dead and try to reconnect and then land you in another pry request.
Probably you can alleviate this to a degree by setting some timeouts on the LiveSocket (which AFAIK inherits all the options from Socket).
Possibly you’d have to adjust some timers on the Elixir side too, I have not tried.
You could also configure your own dbg backend to proxy the existing one and perhaps only pry when given an option.







