vans163
vans163
the signalling thread creates its own socket server now. and 3 types changed in observer.h. Hope this helps.
Benchmarking using wrk (stargate:launch_demo()) reveals this to be true. root@freebsd:~/wrk2 # ./wrk -t8 -c100 -d30s -R25000 http://127.0.0.1:8000/ Running 30s test @ http://127.0.0.1:8000/ 8 threads and 100 connections Thread calibration: mean...
There should be a better way to handle this in rebar3 itself, this solution wont work if rebar3 adds new shell arguments. Closing this and opened rebar3 issue https://github.com/erlang/rebar3/issues/1322
This was closed on rebar3, so reopening.
`rebar_agent:do(compile)` is used, if this happens this is a problem with rebar itself.
Give this a new try please, I have released v0.5.1 which uses `r3:do(compile)` instead of `rebar3_agent:do(compile)`
rebar_agent:do(compile) is used to compile, this ticket should be cross filed to rebar as its a rebar issue.
Give this a new try please, r3:do(compile) is used now. v0.5.1 of rebar3_auto
What is the difference between working in a relx release in dev_mode vs working in development mode with rebar3_auto outside a release? If the reason is convincing enough it could...
@lucafavatella Is it possible to get some more details of what is happening now, and what should be the expected behavior?