Since this morning, when I try to sync from GitHub Desktop after creating a commit, I sometimes get the message:
When I try to push the commit in Git Shell, I get:
SSL read: error:00000000:lib(0):func(0):reason(0), errno 10054
What could be the issue?
It takes around one or two minute between the time I try to push and the time I get the error message (in GitHub Desktop or Git Shell), so I suspect some connection issues on GitHub side (I have checked the robustness of the connection on my side), but I find the message sibylline.
I use GitHub Desktop with Windows 7 SP1 x64 Ultimate.
Change URL from https to http, for me it worked. There must be problem with ssl tunnel. But currently you can start it by switching to http.
I got here because I was looking for a solution, too. I have got an SSL read: error.... (identical to yours) returned as well when I was trying to push a commit. The reason might have been some big files in the commit that you were trying to push to github.
For me, I followed steps https://git-lfs.github.com provides and it seems to solve my problem.
Related
question: I have copied one of my julia project from local pc to a cluster using Linux. When I was trying to run instantiate in Pkg-REPL, ERROR: git repository not found at `https://github.com/JuliaRegistries/General.git occurred. And I have no idea.
enter image description here
what I have checked: I have entered status in Pkg-REPL and it seems everything is well; and there is only one direction logs under ~/.julia
enter image description here
so what caused the problem and how should I fix it? Thank you in advance!
I finally solve this problem by cloning from https://github.com/JuliaRegistries/General.git manually.
cd ~/.julila
mkdir registries and cd registries
git clone https://github.com/JuliaRegistries/General.git and get a new direction General
now I can instantiate without any error occurred!
I am not still clear why the error occurred when I clone this site automatically using instantiate, so this is still a question to be answered.
I'm not sure if these could be the causes, but:
Can the server connect to GitHub? i.e., can you ping www.github.com? It is possible that a work-based server is hidden behind some firewall. Of course, quite odd to not allow outbound traffic.
Also, on your server account, have you had your public key registered with GitHub? It's been a while since I've had to do this, but you may need to also set your username and e-mail address. An easy test would be to just try doing a git clone https://github.com/JuliaRegistries/General.git on the server and see if that is successful. If not, perhaps the error message that it gives will be helpful.
I am setting up DR.Racket for SICP. By following this guide
http://docs.racket-lang.org/sicp-manual /index.html?q=sicp#%28part._.Introduction_to_the__lang_sicp_language%29
But I am not able to download sicp package. Following is the error message I recieved after hitting install.
Resolving "sicp" via https://download.racket-lang.org/releases/6.11/catalog/
ssl-connect: connect failed (error:14090086:SSL routines:ssl3_get_server_certificate:certificate verify failed)
Please explain what to do?
Apologies if I'm telling you things you already know: it appears that certificate validation failed while contacting the racket package server.
There are several things that could cause this, but I have a sneaking suspicion that you have some kind of proxy standing between you and the server that is rewriting your traffic. Is this possible?
One way to test this would be to try installing the package on a different computer, connected to a different network.
(FWIW, I just tested this installation myself, and didn't encounter this problem. So, at a minimum, it's not that the world is broken :).)
I am currently having some issues with heroku. I just installed it and tried to heroku create. It takes my credentials but so far i just get this
! HTTP Error: https://api.heroku.com/login 410 Gone
! Invalid response from API.
! HTTP 410
! {myMail myPw}
!
! Are you behind a proxy?
! https://devcenter.heroku.com/articles/using-the-cli#using-an-http-proxy
I have been looking around for others with that issue but they all were behind a proxy. I am not. I also checked my firewall settings and also tried to run the command line client with admin rights. But nothing has proven to be successful so far. I'll keep trying and post an answer as soon as i figure it out. Maybe someone of you has an idea. Would be appreciated. Thanks in advance and
Greetings Chris
EDIT
Maybe some info. I'm running
Windows 10 Pro (V10.0.15063)
and a basic network setup with a router and DHCP
I had the same problem today.
When I type
heroku
in my Command Prompt, it promotes me to enter my email and after that my password. Then I got the same error message as you.
After that instead "heroku" I typed
heroku login
I entered the same email and password and everything was fine.
Ok. I made it work. Unfortunately I'm not really understanding why this worked which is pretty unsatisfying but I'll tell you what I did. I stumbled on some posts that were saying heroku-cli is outdated if that happens. First I tried to update it with npm using
npm update -g heroku-cli
which basically made heroku stop working alltogether because now the cli reported it needed node >7.X (and I was still running on 6.X). The node update I then made also didn't help because now heroku-cli was unable find the command bash.
In the end I just reinstalled heroku. After that (with at first getting the same error as in the beginning) I first did
heroku update
and after that heroku login worked. Now why I don't really grasp and maybe someone of you guys knows. But the version I had before heroku update was exaclty the same as afterwards
heroku-cli/5.11.12-8ae9780 (windows-amd64) go1.7.5
I found out the heroku.cl was blocked by my antivirus and unblocked it. Now its working flawless.
Updating Heroku worked for me.
heroku update
A lot of people have ask this question but it was 2 month ago with another gitlab version,
I'm using gitlab 5.2 in a fresh debian 7.0 serveur
everything looks Okay on the website but when I run /home/git/gitlab-shell/bin/check I've got this error :
Check GitLab API access: FAILED. code: 302
Check directories and files:
/home/git/repositories: OK
/home/git/.ssh/authorized_keys: OK:
I'm running on a custum ssh port but I'm able to connect.
When pushing I've got this error:
git push -vu origin master
Pushing to ssh://git#apps.ndd.fr:2232/Users/test.git
fatal: The remote end hung up unexpectedly
Thanks for your answers!
I've just got the same error and go look onto the code.
The thing I've found the gitlab_net module going for answer at #{host}/check (gitlab-shell/lib/gitlab_net.rb)
host method is defined as "#{config.gitlab_url}/api/v3/internal", and at the same time config.gitlab_url defined in ./gitlab-shell/config.yml "Should end with a slash" (c) So my web server just returns 302 on a request to remove double slashes.
FYI: That fail is about API and not about web service. So it's non-critical in many cases anyway.
I think it's a minor bug in code and there is a close issue to this: https://github.com/gitlabhq/gitlabhq/issues/3483
I have Master/Slave setup using Win2k8R with SVN 1.6.9 and using TortoiseSVN 1.6.7.
The access is through Apache and using http.
Everything works but when I commit I get the following message:
Error: post-commit hook failed (exit code 1) with output:
Error: The process cannot access the file because it is being used by another process.
This happen when using multiple TortoiseSVN dialog for committing the files in rapid succession. If I use one TortoiseSVN dialog and wait till the commit reply is back then I won't see the problem. In other words, committing one at the time cause no issue.
The post-commit script output is logged.
Even though I get the above error but when I check the Master and Slave repository the files have been replicated okay with no issue.
I am wondering how this issue can be solved.
You should vote this as an issue in the Subversion Issue Tracker.