Why would it be every time I try to install from ios terminal I get a message like:
port 443: Operation timed out.
I'm new to using github. Do I need an account (username/password) with them.
Basically all I've done is open terminaland typed curl -v https://github.com/gruntjs/grunt.git.
Can anyone help me with this. I've googled for ages but none of the suggestions work.
I tried setting the proxy by
export http_proxy="myproxyaddresshere:8080"
Try: $ git clone https://github.com/gruntjs/grunt.git
This would do!
Do I need an account (username/password)
If you want to make changes to grunt or any project on github, you need a github account, then you have do something called forking the project.
Then you pull your forked copy of the project into your local system, make your desired changes and then push the changes to github.
Related
I'm using Jenkins 2.15 (GitHub plugin 1.29.3) based CI for my GitHub core repo. It works fine, but sometimes Jenkins build doesn't update GitHub check status.
I see nothing relevant into Jenkins log.
Any idea how to debug and hopefully fix this issue?
As I know, check status update is just an http request to the status api: https://developer.github.com/v3/repos/statuses/
I experienced a similar behavior with a database. The client application and the database had no errors. Each one was on a different host.
What I did was, create a bash script in host A to perform a ping to host B.
ping www.host_B.com | while read pong; do echo "$(date): $pong"; done >> /tmp/ping-test-$(date +%F).log
Then, when the sporadic error related to the connection of the database occurred, the log file helped me to detect that the error was related to:
Network issues
Latency issues
Internet service provider issues
In your case, you could perform a simple curl to the status api and compare to the sporadic behavior detected.
I have created ssh key using the command ssh keygen and I have added the public key to my bitbucket account and then I have added the key to the ssh agent also, But when I tried to clone repo from bitbucket using sourceTree, I am getting the below Error.
Error: FATAL ERROR: Disconnected: No supported authentication methods available (server sent: publickey)
fatal: Could not read from remote repository.
Please make sure you have the correct access rights
and the repository exists.
and I know this is repeated question but those solution didn't worked for me, So please help.
Well, It was my mistake actually,
SSH Client type was set to PuTTY/Plink in my SourceTree Settings, So I changed it to openSSH and now that issue is no more.
Sorry & Thanks.
I am using SourceTree to access an enterprise GitHub server, and had the same issue all of a sudden start occurring to me even though it has been working fine for over a year and nothing had changed. Apparently, somehow my SSH Client Type was swapped to PuTTY/Plink. Switching it to openSSH again fixed the issue for me by going to Tools -> Options -> General -> then selecting OpenSSH as the SSH Client under the SSH Client Configuration section.
Changing the SSH Client type to openSSH in Source Tree - tools -> Options -> General solved this error for me.
(I posted the following to atlassian.com bug report)
We had the same issue. We noticed that the Pageant (in the icon tray) would not start.
For us it appears that our antivirus was blocking it somehow. Thus we do the following:
disabled the antivirus
uninstall SourceTree (SourcetreeEnterpriseSetup_3.4.6.msi)
installed SourceTree (SourceTreeSetup-3.4.6.exe)
reconfigured SourceTree
We noticed that Pageant was now running and ssh calls worked.
Reenabled the antivirus.
So far so good.
In my case, I was getting same error but the "pageant" program installed was very very old, but worked after updating it (via the putty installer). Credit to https://superuser.com/users/106302/fabian # https://superuser.com/a/404286/658383
So I made changes to my rails app on my local machine that were never committed and that I decided to discard. Decided to rollback to most recent commit by deleting my rails app and all its files, and then cloning my most recent commit from my github repository. Unfortunately
git clone https://github.com/my_username/rails_app.git
results in the following error that cannot be found by just googling:
Cloning into 'sample_app2'...
fatal: unable to access 'https://github.com/IPX-/sample_app2.git/': SSLRead() return error -9806
I was recently pushing to the repo earlier today, even set up an SSH key for my this laptop, but all to no avail.
Why is git clone not working for my own repository?
Possible error due to low internet connection. This error occurred when you try to connect to server through ssl and net connection drop immediately. Or some time due to frequent disconnection. YOu can find more about this here http://flummox-engineering.blogspot.in/2014/04/sslread-return-error-9806-server.html
Possible duplicate of SSLRead() error using Git in Mavericks OS X 10.9.2
Anyhow, the answer mentioned here is that you download SSL and install.
When you have already set up SSH then why don't you access your repo over SSH?
You can use user.name#github.com:<your-repo> and it will not ask you for password if you have actually set-up SSH properly!
Enjoy!
When I create new project in Xcode 5, Am trying to add new server for source control. But am getting error alert like this "The Xcode service is disabled on this server. Please contact your administrator for help".
Please check out how to turn on the OSX Server Xcode service at the following link:
https://developer.apple.com/library/mac/documentation/IDEs/Conceptual/xcode_guide-continuous_integration/200-Adopting_a_Continuous_Integration_Workflow/adopt_continuous_integration.html#//apple_ref/doc/uid/TP40013292-CH3-SW1.
If review of this guide does not fix your issue please let me know more specifics about your environment. If it does help please consider accepting the answer so others will locate the resource.
Important Conceptual Notes:
When you setup a new project and you are offered a server this refers to an OSX Server only (not github or any non-OSX external server):
So basically just make sure the OSX Xcode service is ON or restart your 10.9+ OSX server if possible...
NB: If what you want to do is to push your repository to github.com or code.google.com please see the following links for instructions on getting this to run in Terminal. Once the link between the remote repository and your local directory then Xcode will be able to push updates to your remote repositories (this will be available as a checkbox when you commit your project).
Github Help
Pushing to Google Code
It sounds like you want to add a repository, not an XCode Continuous Integration server.
Adding a server is adding an XCode Continuous Integration server.
Use add repository instead. See the guide in the first link.
It seems like a "Server" in apple's definition is not a BitBucket server or GitHub server, it has to be a server that you host by yourself. Otherwise you are looking at adding a "repository".
I got enlightened by the screenshot below, note the server address:
To set the context, I am trying to use the toto to set up my blog.
I did
$ sudo gem install toto
and the gems were installed properly.
Successfully installed rdiscount-1.6.8
Successfully installed toto-0.4.9
2 gems installed
After that, I tried
$ git clone git://github.com/cloudhead/dorothy.git myblog
but I get the following error
Cloning into myblog...
github.com[0: 207.97.227.239]: errno=Connection timed out
fatal: unable to connect a socket (Connection timed out)
My git http proxy settings are correct
jatin#jatin-ubuntu:~/myblog$ git config --global http.proxy
http://proxy:port
My http_proxy settings are also correct
jatin#jatin-ubuntu:~$ echo $http_proxy
http://proxy:port/
So, I replaced git by http, as
$ git clone http://github.com/cloudhead/dorothy.git myblog
and it worked.
Now, when I do the following
$ cd myblog
$ heroku create myblog
it works till here and I get
Creating myblog...... done
Created http://myblog.heroku.com/ | git#heroku.com:myblog.git
Git remote heroku added
But it fails down here:
$ git push heroku master
and the following error comes up
ssh: connect to host heroku.com port 22: Connection timed out
fatal: The remote end hung up unexpectedly
I didn't know what to do, so after Googling a bit I found that you can't push changes to github using http.
On digging in further, I found this link
how-to-use-the-git-protocol-through-a-http-connect-proxy
which says that you can have your firewall administrator configure the proxy to also allow CONNECT for port 9418, which is the port used by git.
Once they have appropriately configured the proxy, you should then be able to use tools like netcat-openbsd or socat to connect through.
My problem is that I am a student and I can't get around this because I can't reach out to the administrator. I don't know what to do, as I am still stuck looking for an answer.
You added the heroku remote using this URL git#heroku.com:myblog.git. This was probably configured by the heroku create command.
When you push to this remote, it is done via SSH. And this is exactly what the error message indicates: that you (or git) tried to ssh to heroku.com, but couldn't because of your firewall (probably) denied that. With your git push heroku master command, you are not pushing to Github, but to the git repository at Heroku. To push your stuff to Github, you need to git push origin master and use either ssh or http for the transport. The git:// protocol itself does not support pushing changesets but is an unauthenticated re-only protocol.
Currently, Heroku seems to only allow the SSH transport for its git repos and there don't seem to be any direct hooks on Github (see Push from github to heroku without downloading repo). This means to publish your apps on Heroku, you need to be able to push to heroku.com via SSH from your local host.
You can also push to https://cloudhead#github.com/cloudhead/dorothy.git (note the username in the url).
When you push to this remote, it is done via SSH. The error you are getting is because the client could not connect via SSH, most likely because you are behind some type of firewall that is preventing the connection. I used to have this same problem when trying to push to Heroku from work.
My suggestion would be for you to develop locally and then go to some public hotspot to push the changes to Heroku (like a Starbucks).