Skip to content
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 compile silently fails #91

Closed
catamorphism opened this issue Jan 7, 2015 · 4 comments
Closed

rebar3 compile silently fails #91

catamorphism opened this issue Jan 7, 2015 · 4 comments

Comments

@catamorphism
Copy link

$ rebar3 compile
===> Fetching erequest_id
(tchevalier@tchevalier-ltm)
[Tue Jan 06~18:08:39] ~/heroku/hundur $ echo $?
1

The compile command failed, but didn't print a message indicating the failure. If I do this:

$ DEBUG=1 rebar3 compile

I get more info:

[snip]
===> Fetching erequest_id
===> sh info:
    cwd: "/Users/tchevalier/heroku/hundur"
    cmd: git clone https://github.com/heroku/erequest_id.git .tmp_dir193467206960 -b 0.2.1 --single-branch

===>    opts: [{cd,"/tmp"}]

===> Port Cmd: "git clone https://github.com/heroku/erequest_id.git .tmp_dir193467206960 -b 0.2.1 --single-branch"
Port Opts: [{cd,"/tmp"},
            exit_status,
            {line,16384},
            use_stdio,stderr_to_stdout,hide]

===> sh(git clone https://github.com/heroku/erequest_id.git .tmp_dir193467206960 -b 0.2.1 --single-branch)
failed with return code 128 and the following output:
Cloning into '.tmp_dir193467206960'...
fatal: could not read Username for 'https://github.com': Device not configured

Not sure what's going on here, but in any case, rebar3 should be reporting the failure without having to use DEBUG=1.

@tsloughter
Copy link
Collaborator

Damn, yea, terrible user experience. It is because you don't have github https support for private repos setup in your .netrc.

Will leave this ticket open until we have it provide a useful error message.

@catamorphism
Copy link
Author

Once I fixed my .netrc:

$ rebar3 compile
===> Fetching erequest_id
===> Fetching midjan
===> Fetching dinerl
(tchevalier@tchevalier-ltm)
[Wed Jan 07~13:24:12] ~/heroku/hundur $ DEBUG=1 rebar3 compile
[snip]
===> Fetching dinerl
===> sh info:
    cwd: "/Users/tchevalier/heroku/hundur"
    cmd: git clone https://github.com/SemanticSugar/dinerl.git .tmp_dir393704963216 -b v1.0.1 --single-branch

===>    opts: [{cd,"/tmp"}]

===> Port Cmd: "git clone https://github.com/SemanticSugar/dinerl.git .tmp_dir393704963216 -b v1.0.1 --single-branch"
Port Opts: [{cd,"/tmp"},
            exit_status,
            {line,16384},
            use_stdio,stderr_to_stdout,hide]

===> sh(git clone https://github.com/SemanticSugar/dinerl.git .tmp_dir393704963216 -b v1.0.1 --single-branch)
failed with return code 128 and the following output:
Cloning into '.tmp_dir393704963216'...
fatal: did not receive expected object 68f43be15accbd4403af68315c9ac997ad8e46cf
fatal: index-pack failed

I'm pretty sure this is the same bug, since both issues involve git failing, but in different ways. Just thought I would document this other failure case too.

@shijiang1130
Copy link
Contributor

Hi catamorphism,
could you try modify the git config file, add the line below to see if fix the issue.
compression = -1

Here is the same symptom, but another way to resolve: http://git.661346.n2.nabble.com/Large-pack-causes-git-clone-failures-what-to-do-td5481488.html

@tsloughter
Copy link
Collaborator

Oh, we forgot to close this. @shijiang1130 it was a github issue. Thanks.

Closing this now even though I said I'd leave it open until I made error messages better, just to make it less confusing :)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants