We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
when I set the rebar.config the follows (this is error syntax) in rebar app:
{sub_dirs, ["rel","."]}.
In that time,my computer will break down, the cpu and mem are go out.
➜ ~ ps -ef |grep beam wanjun 3909 3906 8 18:50 ? 00:00:29 /usr/lib/erlang/erts-5.9.1/bin/beam.smp -B -- -root /usr/lib/erlang -progname erl -- -home /home/wanjun -- -boot start_clean -noshell -pa rebar/rebar/ebin -run escript start -extra /usr/local/bin/rebar compile skip_deps=true wanjun 4326 4219 0 18:56 pts/5 00:00:00 grep beam ➜ ~ kill -9 3909
when I kill the process, I can see so many error in the sublime text console, 16723 lines data, it is repeat this:
ERROR: infinite loop detected: sub_dirs entry "." in /home/wanjun/pro/erlang/rebarapp/rebar.config
➜ ~ rebar -V rebar 2.1.0-pre R15B01 20130710_094740 git 2.1.0-pre-140-g620c4b0 ➜ ~
The text was updated successfully, but these errors were encountered:
No branches or pull requests
when I set the rebar.config the follows (this is error syntax) in rebar app:
In that time,my computer will break down, the cpu and mem are go out.
➜ ~ ps -ef |grep beam
wanjun 3909 3906 8 18:50 ? 00:00:29 /usr/lib/erlang/erts-5.9.1/bin/beam.smp -B -- -root /usr/lib/erlang -progname erl -- -home /home/wanjun -- -boot start_clean -noshell -pa rebar/rebar/ebin -run escript start -extra /usr/local/bin/rebar compile skip_deps=true
wanjun 4326 4219 0 18:56 pts/5 00:00:00 grep beam
➜ ~ kill -9 3909
when I kill the process, I can see so many error in the sublime text console,
16723 lines data, it is repeat this:
➜ ~ rebar -V
rebar 2.1.0-pre R15B01 20130710_094740 git 2.1.0-pre-140-g620c4b0
➜ ~
The text was updated successfully, but these errors were encountered: