1
2
3
4
5
6
7
8
9
10
11
12
13

FAT [20121215-15:49:46.803] HttpServer: A server service client threw an exception
FAT [20121215-15:49:46.803] HttpServer: com.twitter.finagle.WriteException$$anon$1: java.net.ConnectException: connection timed out
FAT [20121215-15:49:46.803] HttpServer:     at org.jboss.netty.channel.socket.nio.NioClientSocketPipelineSink$Boss.processConnectTimeout(NioClientSocketPipelineSink.java:391)
FAT [20121215-15:49:46.803] HttpServer:     at org.jboss.netty.channel.socket.nio.NioClientSocketPipelineSink$Boss.run(NioClientSocketPipelineSink.java:289)
FAT [20121215-15:49:46.803] HttpServer:     at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110)
FAT [20121215-15:49:46.803] HttpServer:     at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603)
FAT [20121215-15:49:46.803] HttpServer:     at java.lang.Thread.run(Thread.java:722)
FAT [20121215-15:49:46.803] HttpServer: Caused by java.net.ConnectException: connection timed out
FAT [20121215-15:49:46.803] HttpServer:     at org.jboss.netty.channel.socket.nio.NioClientSocketPipelineSink$Boss.processConnectTimeout(NioClientSocketPipelineSink.java:391)
FAT [20121215-15:49:46.803] HttpServer:     at org.jboss.netty.channel.socket.nio.NioClientSocketPipelineSink$Boss.run(NioClientSocketPipelineSink.java:289)
FAT [20121215-15:49:46.803] HttpServer:     at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110)
FAT [20121215-15:49:46.803] HttpServer:     at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603)
FAT [20121215-15:49:46.803] HttpServer:     at java.lang.Thread.run(Thread.java:722)

It turns out I needed to set up my ClientBuilder a little differently:

1
2
3
4
5
6
7

  val client = ClientBuilder()
    .codec(Http())
    .hosts("localhost:80")
    .tcpConnectTimeout(2.seconds)
    .requestTimeout(55.seconds)
    .hostConnectionLimit(5)
    .build()

The important bits, that don’t appear well documented are tcpConnectTimeout and requestTimeout. The normal ‘timeout’ usually used on the ClientBuilder is not what you want.

This was more a note for me - but figured people Googling might find it useful also.

Why? Well, for me the point of writing everything like it’s going to be open source seems like a great way of doing things. It’s a great philosophy to have. Seriously.

This is especially important now that degrees are just so damned expensive. According El’Reg, you’re looking at £27k for your degree. Wow!

Personally, when I look at people’s CVs, the first thing I’ll do is Google them. Then, I’ll take a look at their Github profile. Then I look at their education. It’s important that if they did a degree, they did well - but it doesn’t matter if they didn’t do one at all.

Originally from QuestionCopyright.org

So imagine the scenario. You’ve done a load of commits and you’re not ready to merge them back into master (or, even worse you’re in master) and you realise you made a massive mistake a few commits back and you need to just squash all the correction commits into it:

1
2
3
4
5
6
7
8
9
10
11
12
13
14

commit 6e0fa1b21e760aee2391f73c4905244a229abe8b Author: Lee Packham
<xxx> Date: Sat Jul 2 12:47:31 2011 +0100

More tidy up (I'm a muppet)

commit abe08fd948f81f3366bc9a647e0d0c24ffe5fdc6 Author: Lee Packham <xxx>
Date: Sat Jul 2 12:46:14 2011 +0100

Tidy up

commit caefc1c0a8903009af2be8cd37df1ac40366fcce Author: Lee Packham <xxx>
Date: Sun Jun 19 08:21:03 2011 -0700

Initial commit

Well that’s crap really isn’t it? So how do we go about sorting this? Well, we make a good use of rebase and tags to achieve this. There’s a nice answer to this on Stack Overflow - but I’ll replay it here. Props to Charles Bailey for this process.

So, here’s how we fix this:

1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16

# Checkout the top commit in a detached branch git checkout
6e0fa1b21e760aee2391f73c4905244a229abe8b

# Now, do a soft reset back to the original commit git reset --soft
caefc1c0a8903009af2be8cd37df1ac40366fcce

# Now commit --amend it to squash it all git commit --amend

# Then, tag this new detached commit git tag tmp

# Now go back onto master git checkout master

# Awesome now do a quick rebase and it'll replace the upstream with tmp git
rebase --onto tmp 6e0fa1b21e760aee2391f73c4905244a229abe8b

# No need for tmp now git tag -d tmp

Not overly simple - but brings, in this case, master to where I wanted it to be!

This will mean your app will no longer crash - so fairly useful.

I’ve kept my e-mails the same, for now, however - leenux.org.uk has been my primary domain for nearly a decade (10 years this November), so I’ll have to keep it running regardless. This’ll just be the blog for now.

I came along fairly late in the day in all this having only joined in January of this year. I never guessed that by now I’d be working for Twitter as a Software Engineer. I’m totally stoked.

I’ll still be working on mobile clients - and hopefully I’ll get more time to work on Chrome hacks.

So, congratulations everyone! Special congratulations to Iain… it proves that scratching an itch really can lead you down paths you never expect. Let this be a lesson to Software Engineers / Programmers everywhere.

This is why you should always be careful what you throw in the trash. ALWAYS SHRED YOUR STUFF. This guy, and a guy on the other side of the road, systematically working their way up said road scavenging.

The new TweetDeck for iPhone still lets you add as many columns as you want and swipe through to view different streams, but you also get a unified Home column, which can combine your Twitter and Facebook streams into one. The app has nice subtle touches, such as the diagonal swipe to see more Tweets from the same account (my favorite). And instead of timestamps cluttering each Tweet, the timestamp changes at the top as you scroll through your stream. If you want to jump to the top to the most recent Tweet, just tap the actual time (yeah, someone had to point that one out to me too, but these are the kinds of hidden features power users love).

• Uncheck KB982018 and install all other updates
• Reboot
• Install KB982018 on its own
• Reboot And you’re done.

Yes, really, it’s that stupid. Enjoy!

1. Load up simulator
2. Grab a finder window
3. Drag jpg/png into iPhone Simulator window
4. It’ll open up Safari
5. Long click on Image
6. Save Image
7. (If this is the first time on this emulator) Long click on Image and Save Image again This way you can use the picker and everything. Great. Better than the solutions of random folders in ~/Library I think

#

#

#

#