-
-
Notifications
You must be signed in to change notification settings - Fork 5.5k
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
Pkg.update() hangs when updating private github repo #16373
Comments
I hope #16308 will fix this. |
Great, thanks! I'll follow along and let you know. |
I pulled your credentials branch (#16308) and tested it. I ran
|
Can you reproduce this segfault? I do not see any julia functions in the stack trace. |
I rebased your branch on the latest master and tried again. I have run |
Can you post an exception stack trace when you interrupt hanging repo update? If you are on latest master there should be plenty of output from |
Looks like when I tried earlier today I was on the wrong Julia branch, oops! Now when I tried the correct branch it was improved, but still not totally fixed. Most of the time
In the second failure it hanged, but in a different place than before. It's during "Computing changes...." When I interrupted that I saw this rather uninformative trace:
|
Just to make sure we're on the same page, here's my Julia version (the 11 commits are all yours): Version 0.5.0-dev+4167 (2016-05-18 18:54 UTC) |
The SIGINT segfault is more general issue then the package manager. It's a tricky one. I got one sometime ago, #11382, but could not reproduce it. As for exceptions during |
I have been getting the SIGINT segfault most of the times that I have to interrupt As for my password, I checked and the problem occurs regardless of whether I have unicode characters or purely ascii characters. The string printed ( |
I found cause of the segfault, it's strings from |
Great, I'm glad to hear you found it! Let me know when you want me to test it again. |
@Cody-G Could you check latest update? |
What was the fix? Can we add a test that would have hit the problematic code path? edit: if it was only |
I think we're getting close. The very first time I ran
|
I was able to trigger the same error a couple more times by waiting a few minutes between |
I see, update doesn't stop after |
I also got this today: in the latest 0.5 master, Pkg.update() hanged. It prompts for my Github username and password but doesn't respond after I enter them. I don't have any private repos, but I had a dirty package pointing to a forked repo that I deleted after merging a PR. After running Pkg.free() the problem was gone. |
try again on latest master, #17539 should fix this. if not fixed, leave a comment and we'll reopen. |
In the latest 0.5 master,
Pkg.update()
often hangs indefinitely when updating a private repository. It prompts for my Github username and password but doesn't respond after I enter them. If I press ctrl+c several times I can abort updating that package, and then some (but not all) of my other private repositories are able to update successfully.The text was updated successfully, but these errors were encountered: