Install a better version of GIT on Amazon EC2 default instance

By , Monday 14th January 2013 10:27 am

I was doing some development on an Amazon default EC2 instance and wanted to commit some changes back to a repository using `git commit -p`, flag ‘-p’ not recognised, boo!

Turns out the default version of GIT that comes with the EC2 instances is 1.7.4.X. I’m not sure (and can’t easily find) what version the patch feature was added to `git commit`, but I have an install of 1.7.7.X available and it appears to be in there  (update – git commit patch added in 1.7.6).

Anyway I had a quick look around the interwebs to find a repo/rpm for a newer version of GIT so I could make my patch commit. I eventually discovered that version is sitting in the ‘amzn-preview‘ repository which is sitting on the box already. In order to upgrade GIT therefore you simply do:

sudo yum install --enablerepo=amzn-preview git

This will get you a more recent version, and the very useful patch feature.

An error has occurred: {“bytesParsed”:0,”code”:”HPE_INVALID_CONSTANT”}

By , Saturday 12th January 2013 2:38 pm


I’ve been writing a new application in Nodejs, using websockets (, this application is deployed using the PaaS Nodejitsu.  Everything has been going great and I’ve been surprised how easy it has been to create a realtime application using Deployment has also been a breeze with Nodejitsu’s tools.  I develop on a Linux machine myself but the other day I passed the details to someone using a windows machine running internet explorer.  The application stopped working with an error message, a redeploy didn’t help. The error I was presented with was as follows:;

An error has occurred: {“bytesParsed”:0,”code”:”HPE_INVALID_CONSTANT”}

As I haven’t uploaded any new code in about a week I made the incorrect assumption that something had gone wrong on nodejitsu’s side and so dropped them a tweet to let them know as they are still in beta as far as I understand.

Within 90 minutes I’d got a reply from Nuno Job (@dscape) from Nodejitsu letting me know that there was an issue with Internet Explorer,, and Joyent’s servers. He also included a workaround, and a link with further details. Excellent support!

From what I’ve understood the proxies used at Joyent don’t like non-HTTP response (from the flashsocket) and so prevent any further connections to the domain (please correct me in the comments if incorrect).

The solution is to turn off flashsocket as a transport when configuring as follows:

var io = require('').listen(80);

    io.set('transports', [


I hope this helps anyone that comes across the same issue, the original solution/explanation came from

With this in place the app sprung back into life. I just really need to report to users with browsers that don’t implement websockets that they need to use something more modern…





Panorama Theme by Themocracy

1 visitors online now
0 guests, 1 bots, 0 members
Max visitors today: 16 at 08:14 am UTC
This month: 17 at 19-09-2017 09:35 pm UTC
This year: 45 at 02-01-2017 10:28 pm UTC
All time: 130 at 28-03-2011 10:40 pm UTC