Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    text
    copied!<p>Looks like a server issue (i.e. a "GitHub" issue).<br> If you look at <a href="http://markmail.org/message/tzaouhiolfbthvji#query:%22RPC%20failed%22%20%22HTTP%20code%22%20result%2022+page:1+mid:efulsrjmzsdzxjoh+state:results" rel="nofollow noreferrer">this thread</a>, it can happen when the <code>git-http-backend</code> gets a corrupted heap.(and since they <a href="http://twitter.com/github/statuses/12648958965" rel="nofollow noreferrer">just put in place </a> a <a href="http://github.com/blog/642-smart-http-support" rel="nofollow noreferrer">smart http support</a>...)<br> But whatever the actual cause is, it may also be related with recent <a href="http://status.github.com/" rel="nofollow noreferrer">sporadic disruption in one of the GitHub fileserver</a>.</p> <p>Do you still see this error message? Because if you do:</p> <ul> <li>check your local Git version (and upgrade to the latest one)</li> <li>report this as a <a href="http://support.github.com/" rel="nofollow noreferrer">GitHub bug</a>.</li> </ul> <hr> <p>Note: the <a href="http://github.com/blog/642-smart-http-support" rel="nofollow noreferrer">Smart HTTP Support</a> is a big deal for those of us behind an authenticated-based enterprise firewall proxy!</p> <blockquote> <p>From now on, if you clone a repository over the <code>http://</code> url and you are using a Git client version 1.6.6 or greater, Git will automatically use the newer, better transport mechanism.<br> Even more amazing, however, is that you can now push over that protocol and clone private repositories as well. If you access a private repository, or you are a collaborator and want push access, you can put your username in the URL and Git will prompt you for the password when you try to access it.</p> <p>Older clients will also fall back to the older, less efficient way, so nothing should break - just newer clients should work better.</p> </blockquote> <p>So again, make sure to upgrade your Git client first.</p>
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload