Open drozzy opened 8 years ago
We're also getting this consistently on Windows 10. The first time we run, say, rebar3 shell
, everything works fine. When we re-run rebar3 shell
later one, things fail unless we clean
first. I've also only observed this on Windows 10 so far.
I don't have a way to replicate because of no access to windows 10 -- unless they finally offer some sort of free VM I can run locally?
Note that removing only the *_dtl.beam
files from _build
also helps - full clean isn't needed.
As for free VM, they actually do offer that! https://developer.microsoft.com/en-us/windows/downloads/virtual-machines
If there's anything further I can do to help with resolving this, please let me know, happy to help.
Got someone to run it with DEBUG=1
:
===> Provider: {default,compile}
===> Provider: {erlydtl,compile}
===> Running erlydtl...
===> sh info:
cwd: "c:/project"
cmd: grep -o [^\"]*\\\.dtl[^\"]* c:/project/priv/templates/public.dtl
===> opts: [{use_stdout,false},return_on_error]
===> Port Cmd: cmd /q /c grep -o [^\"]*\\\.dtl[^\"]* c:/project/priv/templates/public.dtl
Port Opts: [exit_status,{line,16384},use_stdio,stderr_to_stdout,hide,eof]
Just gets stuck at "Running erlydt..." sometimes.
Running
rebar3 clean
and the running compile again fixes it.Running Windows 10.