-
Notifications
You must be signed in to change notification settings - Fork 510
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
rebar3 new lib
hangs when run in a non-empty directory
#4
Comments
Do these files exist and could you provide a sample of rebar.lock that seems to trigger this? |
They don't exist in the current working directory, no. I'm not sure where else it would be looking. |
Ah, ok, I assumed it would be one of the files in the non-empty directory. Here's a sample run for me on a ubuntu box:
Let's try the same on a mbp (running an older OSX, 10.7.5):
I can also reapply things otherwise. There's a possibility the program gets blocked up somewhere when it scans its own escript data rather than when it consults the lock file, but without reproducing the bug it's gonna be hard to figure it out :/ |
I'm sure it is getting beyond reading for the lock file. But yea, unless @catamorphism can give us more information on reproducing I'm not sure we should even leave this ticket open... Do you have another computer to compare results with and see what is different between the setups? |
Sorry, this got lost in my inbox. I'll try to reproduce it. |
Should I just close this? :) |
Well I'll be... I just reproduced this! So leaving it open obviously and now digging into it. |
upgrade to relx v4.3.0-emqx-3
If I run:
DEBUG=1 rebar3 new lib squirrels
in any non-empty directory, I get this output:
and then it hangs forever. If I make a new directory and cd into it first, it succeeds.
The text was updated successfully, but these errors were encountered: