Continue reading »]]> I’ve recently been working on setting up a rails app for a site I’m building for one of my side projects.  While I’ve mostly been working on this in my spare time, I decided that it would be important, to one day be able to deploy it to a larger audience (like friends and family). After trying to get rails set up on my old hosting, and being told that Rails 3 wasn’t supported. I recently moved to Vexxhost. Two things enticed me: 1) they’re Canadian; 2) Their hosting is bloody cheap.

So after moving my PHP sites over, I got to work on deploying my currently simple rails app.  And that’s when I hit a problem.

The Problem

ExecJS::RuntimeError in Home#index

Showing /home/jrstarke/apps/___/releases/20120128224905/app/views/layouts/application.html.erb where line #6 raised:

FATAL ERROR: v8::Context::New() V8 is no longer usable (in /home/jrstarke/apps/___/releases/20120128224905/app/assets/javascripts/charities.js.coffee)

Now if you’re finding yourself  in a similar situation, Stop. Take a breath. You’re not very far.

The reason you are finding this is because Rails is clever. The .erb and .js.coffee files in application are compiled, compressed, and this all happens dynamically. They call this the ‘Asset Pipeline’.

The problem is that if you’re shared hosting is anything like Vexxhost (and I imagine most that use cpanel are), their servers in their shared hosting are based on efficiency.  This compiling of assets dynamically takes time and resources, and really, once you’d deployed it to the server, they don’t usually change much (with the exception of a new version, but then that won’t change much either until the next version).

The Solution

It turns out that the solution isn’t all that hard, in fact, most of it I found through a great article on the Ruby on Rails site about The Asset Pipeline – In Production Environments.

The trick is that you essentially need to turn off the asset pipeline. During the dynamic compilation on the fly of assets into a more static compilation. Without further ado, to the solution.

First you need to go into your config/application.rb and disable the application pipeline. You will look for the following line:

config.assets.enabled = true

and turn it to false

config.assets.enabled = false

Next, next go to your Gemfile and comment out the following 3 lines:

gem 'sass-rails', " ~> 3.1.1"
gem 'coffee-rails', "~> 3.1.1"
gem 'uglifier'

These are all the changes we need to make, but before we can deploy the application, we need to compile the assets, ourselves. This is where you will use the following line.

bundle exec rake assets:precompile

At this point use whatever tool you normally use to deploy your app (in my case, Capistrano). If you’re using Capistrano, don’t forget to commit the new assets that would have just been created in your public/assets folder.

Next you’ll need to log into your cpanel, or whatever actually controls your app, stop and restart it. Even if your deploy tool (like Capistrano) just said it restarted your app, don’t believe it, just restart it. This part caught me for a few hours trying to fix this bug. Even though Capistrano said it restarted the app, it still seemed to hold onto the old gems (sass and coffee) until I actually restarted.

With any luck, try your app now, and if your system is anything like mine, it will have worked.

Continue reading »]]>

The Problem

I recently I’ve been having some problems with my MacBook Pro.  At first, I would seem to get disconnected from the internet randomly.  After a few weeks, I finally figured out what the pattern was to the problem.

One morning sat down on the couch, opened my MacBook, and as was becoming normal, I was unable to connect to the internet. The AirPort icon on the menu bar was fully black (meaning that the signal was good).

So I went into the browser and tried to to the router address.  To my surprise, I could fully connect to router. I mean fully. I could log in. I could change the settings. I could ping different websites. It all worked flawlessly. But as soon as I went back to my browser and attempted to connect to a website, any browser, it would complain that I wasn’t connected to the internet.

I would turn off the Wi-Fi a few times, and eventually it would connect fully. So then an idea came to me: Maybe it was related to the fact that I just woke it from sleep. I thought back. Every time I could remember, I had just opened the computer, and it would have difficulty connecting.

So I tried it. I made sure I could access different websites. All signs were a go. Then I closed the lid, and waited for the status light to start flashing. After it did, I would wait a few seconds, and then open the lid. I logged in, opened Chrome, and tried gmail. Gmail is currently unavailable it would tell me. So I opened Safari, and tried again. Same story. After going to the AirPort icon turning it off and on a few times, it came back. I decided to try it again. Sure enough same story. So I tried it a few more times.

After having successfully reproduced this exact approach 6 times, I decided it was time to call Apple. I talked to a rep one day, who walked me through a few steps, that failed to get any results, and before we could go through everything, I had to leave for a meeting. I called back a few days later, and got a Wonderful rep. named Ryan. After 17 minutes on the phone, my problem was solved. I was ecstatic.

The Solution

So the solution to the problem was actually pretty simple. I post it here, so that it might help others (or me if the problem recurs sometime). Remember to back up before hand, as it is possible that you might lose something.

I would also recommend storing your Wi-Fi password on your computer (especially if your password is as complex as mine is).

Here’s what worked for me:

1. Open Finder.
2. From the Menu at the top, choose ‘Go’ -> ‘Computer’.
3. Open your hard drive (probably called ‘Macintosh HD’).
4. Open the ‘Library’ folder.
5. Open the ‘Preferences’ folder.
6. Locate the ‘SystemConfiguration’ folder (likely at the bottom).
7. Drag this folder to your desktop (as far as I can tell, this is to back it up incase something goes wrong)
8. Once the copy is complete, drag the original to the trash.
9. In Finder, open Applications (If you don’t have it on the sideback, use ‘Go’ -> ‘Applications’).
10. Open the ‘Utilities’ folder.
11. Open ‘Keychain Access’.
12. Select ‘login’ from the list of Keychains.
13. In the list to the right, locate an object with the name of your wireless network.
14. Select it and press ‘delete’ on your keyboard.
15. Select ‘System’ from the list of Keychains.
16. Repeat steps 13 and 14 above.
17. Restart your MacBook.
18. Once your computer has restarted, connect to your wireless network.

With any luck your computer will now no longer have issues with your wireless network. This worked perfectly with my D-Link DIR-655 router, on which I could reproduce the wireless network issues flawlessly. Since I performed the steps above, my wireless connection has worked flawlessly.

Continue reading »]]> I’m Looking for advice as to what the best software is for creating online communities.

I’m currently trying to set up a Graduate Students’ Association in my Computer Science department at the University of Victoria.

After talking to a number of Graduate students in my department about what they think would be useful to them, I received a number of great suggestions. Based on the suggestions, I came up with 3 features that I think would be useful:

• A Blog: Which will allow the Grad. Association to keep grad students informed about important upcoming events.
• A Forum or discussion board: Will allow grad. students to discuss whatever they feel is important to them or their work.
• A Wiki: This will allow grad. students to easily create useful resources for other grad students.

There are many possible choices, but it all seems to come down to trade-offs.

As A Service or Host your own

There are two major options for hosting the community. You can either choose to use an As a Service model, where someone else manages the infrastructure, or the Host your own, where you take the software and run it on an infrastructure you control.

The obvious trade off here is Control for maintenance and cost. By going with an as a service, you will decrease costs, and maintenance, but you also decrease your control. By hosting your own, you increase the three.

In the maintenance category, I would like to reduce as much maintenance as possible, as this will likely be run by busy grad students. At the same time though, if we lose all control, we are completely at the liberty of the service to decide what we can do, and how long we can keep it up.

Separate Services or an All-in-one

Again, it is possible that we can use a number of different systems (such as a blog system, a forum and a wiki), or we can find a system that does all three.

In this case we have a trade off between consistency and maintenance versus precision. Of course, if you use 3 systems, you have to deal with maintaining 3 systems, and if you have 3 systems, it is unlikely that the three systems can be consistent.

In the precision category though, any one system will likely be good at a small number of features, and will be less good a others. So by going three systems, they’ll likely be better at the particular thing they do.

For this, I’d like to make the ease of use as easy as possible. If it is really hard for the users to go from one aspect to the other, like the discusion forum to the wiki or the blog, they are less likely to do it, unless it is absolutely necessary. If it’s not possible to link to the other systems consistently, this will be particularly hard.

Community Advice

I’ve use WordPress for blogs before, and they work pretty well. I’ve also considered CMS systems like TikiWiki, but it appears to be particularly buggy. I’ve also used Drupal, and it’s particularly bad for maintenance (which makes me die a little inside).

So this is where I look for advice from the community. What software can you recommend?

Continue reading »]]> Are you having some weird networking problems and want to report a bug to Google Chrome? The most helpful thing you can do to speed up the process is get a network log so that the Chromium team can have a better chance at diagnosing the problem.

In this tutorial, we will walk you through how to collect a Chrome Net-Internals log, and a WireShark Capture.

Pre-requisites:

• Google Chrome
• Wireshark (Download)

What is Wireshark?

Wireshark is a tool for collecting network traffic.  This will allow the Chrome team to get a better idea of what might be causing the network issues.

Reduce Background Noise

Before attempting to make a network log, it is important to try to reduce the background noise.  Normally our computers have a number of programs running in the background, many of which are connecting to external sources.  To give yourself the best chance for success, turn off all unnecessary programs, for the duration of the log.  After you finish, feel free to turn everything back on.

Collecting the Logs

To collect your network logs, perform the following steps:

1. Close Google Chrome and all it’s windows
2. Restart Google Chrome (if it isn’t already open)
3. Open the Net-internals page in a new window or tab (make sure to leave this open) using the following address:

   about:net-internals

4. Open Wireshark
1. From the Capture menu, select Interfaces
2. Find the Description describing your network interface (It will likely have the growing number next to it). Press the Start button to the right of this connection
5. Return to Google Chrome
6. Open a new tab or window and perform whatever operation you want to log (For example, go to gmail.com if you want to demonstrate a slow loading behaviour). Continue until you feel you have a sufficient sample (in the case that it never completes)
7. Open the net-internals page you left open.
1. Under Dump data press the Dump to file button
2. This log will be downloaded to your downloads folder
8. Go to Wireshark
1. From the Capture menu, select Stop
2. From the File menu, select Save As…
3. Enter a descriptive File name (for example ‘gmail-capture’) and for convenience, save it to a location you will remember (such as “My Documents”)

You will now have both a Google Chrome net-internals log, and a wireshark log. Make sure to keep track of where you saved them, and when appropriate, attach them to the bug report.

If you have any questions about this tutorial, please let me know.

Continue reading »]]>

Update: After further testing, the issue seems to be with the NSS-SSL library, rather than SPDY, however the steps below will still likely resolve your speed issues.

Update #2: I am no longer having this issue. It appears to be some odd interplay between the NSS-SSL protocol in Chrome/Firefox and the Traffic shaper at my University, that has since been reconfigured. This means that it is now more important than ever that if you’re experiencing this issue, to report it to the Google Chrome team.

Are you trying to connect to your Gmail, and it seems to take forever to connect? What about Google Docs? Google Plus? All of the above? It might not be Chrome that is the problem, but actually Google’s SPDY protocol behind the scenes.

So what is SPDY? It is a protocol that Google uses, where it keeps a single persistent connection to Google for all of your Google Accounts information. This is utilized by a number of Google Services, including Gmail, Google Docs, and most recently Google Plus. When this is working properly, it allows Google to do what Google does best: Speeding up the web. However, when it fails, it will bring down your Google world, in a thunder of Loading icons.

It it Google Chrome?

The most important first step is it make sure that the problem is actually Google Chrome. To do this, try a different web browser, such as Internet Explorer if you’re on Windows, or Safari if you’re on a Mac.

If you tried a different web browser and the problem still happens, then it is likely due to a different problem, such as a slow internet connection. If however tried the same thing in a different web browser, and it worked fine, then it is probably Google Chrome.

Google knows about this issue (I know, because helped provide information for one of the bug reports), but so far they haven’t narrowed it down.

Collect a log

If you are finding that you have a problem like this, then it might be useful to provide some details to the Chrome team so that they can hopefully make it better.  At this stage, this is optional, but highly encouraged.  This will be your best bet at getting any Google Chrome issues resolved though in the long run.  If you are willing to collect a log, you can do so by following my tutorial How to collect a Network Log for Google Chrome.

The Fix

Disclaimer: This fix is only temporary, and your best bet is to comment on the open Google Chrome Issue for this phenomena.

The good news is that there is a solution you can use for the problem (although it is temporary, as I will cover after). This wasn’t discovered by me, but rather one of my colleagues (Christoph Treude). Essentially what you have to do is disable spdy and Chrome’s enhanced SSL, which can be done using the following steps:

Windows

• Right click on the short-cut you’re using to start Chrome
• Select Properties
• Modify Target from

• ...\chrome.exe"

  into

• ...\chrome.exe" --use-spdy=off --use-system-ssl

  (note: the command line arguments have to go after the quotation marks)

• Click Apply
• Close all Chrome windows
• Restart Chrome

Mac

• Open the terminal (In your Applications -> Utilities folder)
• Type into terminal to change to Chrome’s Directory using:

  cd /Applications/Google\ Chrome.app/Contents/MacOS

• Rename Google Chrome to Chrome in the terminal:

  mv Google\ Chrome Chrome

• Copy the following 3 lines for the contents of our execution script:

  #!/bin/sh
  # This will execute your Google Chrome with SPDY disabled, and set it to use your System SSL
  /Applications/Google\ Chrome.app/Contents/MacOS/Chrome --use-spdy=off --use-system-ssl

• Type the following into the Terminal to make a file from what you just copied:

  pbpaste > Google\ Chrome

• Type the following into the terminal to it so our new Google Chrome can run:

  chmod +x Google\ Chrome

• Close Google Chrome using the Apple menu, or Command-Q:
• Restart Google Chrome

If you had this problem and this solution worked for you, I would recommend you add your voice to the discussion on the bug, as during my last correspondence, they suggested that this might be a problem localized to my network (which it might, but I suspect it isn’t). This solution is only temporary, as if you end up creating a new shortcut somewhere, or you update Google Chrome, you will likely have to redo the fix, or the problem may come back.

Collect a Log (If you didn’t above)

If you found this solution worked for you, but you didn’t collect a log above, perhaps now would be a good time to do so.  However, first we will have to disable the fix above (as the problem will not exhibit itself while the fix is in place). Don’t worry, once you have your log, you can easily turn it back on using the steps above.

Disable fix on Windows

• Right click on the short-cut you’re using to start Chrome
• Select Properties
• Modify Target from

• ...\chrome.exe" --use-spdy=off --use-system-ssl

  into

• ...\chrome.exe"

• Click Apply
• Close all Chrome windows
• Restart Chrome

Disable Fix on Mac

• Open the terminal (In your Applications -> Utilities folder)
• Type into terminal to change to Chrome’s Directory using:

  cd /Applications/Google\ Chrome.app/Contents/MacOS

• Rename Chrome back to Google Chrome in the terminal:

  mv Chrome Google\ Chrome

• Close Google Chrome using the Apple menu, or Command-Q:
• Restart Google Chrome

Collecting the Log on Both

So you’ve decided to help out? I’m glad, this will increase both of our chances at having this resolved.  As I mentioned above, you can collect your Network Log by by following my tutorial How to collect a Network Log for Google Chrome.

Submit to the Issue

If you found that this worked for you, you’re not alone, but unfortunately, as I mentioned above, this solution is only temporary, and you will likely need to redo it the next time you update Google Chrome, or change your shortcuts.  So perhaps now would be a good time to help Google Chrome find a long term solution.   There is already an open issue for Google Chrome about this phenomena, and you can easily submit your information to that issue.  If you need help doing so, let me know, but the Network Logs mentioned above would be highly beneficial to this process.

Could this be better?

So what do I think would be a better solution? For the most part, the average user doesn’t even know what Google Chrome is doing behind the scenes.

The solution above would work, but it isn’t exactly, user friendly. I suggested that in a case like this, perhaps after a few seconds of attempting to connect with SPDY (Google themselves have suggested that users spend less time at slow pages), and not getting any data (which Will Chan said was the case in my case), maybe it would be a good opportunity to say to the user that it’s failing to connect with one method, and to attempt connecting with another.

In this case, the system could try something like the solution above does, disable spdy and ssl, and try then. Sure it’s not a perfect solution, but unless you have to do something explicitly in Chrome (which few people do), this would probably stop you from Switching to an alternative browser.

Continue reading »]]> So last weekend, I wrote on Google Plus about how I was looking for a new side project. Although I still haven’t decided on one, I did decide that as I find one, it might be fun to document the journey and the lessons learned.

Lesson one: Finding a side project is hard.

You always want to have something that is going to be meaningful, and perhaps even help people (it’s always easy to minimally do something that helps yourself, until you actively try to do this, then it’s next to impossible to notice any problems you are actually finding.

What I’ve figured out so far:

• Probably something’s technology based.
  • It’s something I’m skilled at, so I might as well utilize that right?
• Not necessarily software engineering based.
• I’d like to do something that can help someone.
• Having kids does not apply. I just don’t feel like I’m ready for kids yet.
• I would be eager to incorporate some new technologies, if they apply, just for the experience:
  • iOS
  • HTML5
  • Windows Phone
  • Android
• Although I enjoy the odd game, I am not a game designer, and would prefer something that helps with productivity, although I am open to suggestions.
• I have both Windows and Mac machines at my disposal, as well as an iPhone and iPad.
• Money is a bonus, not the goal.
  • I’ve run a small tech support business before. The money was decent, but it was rarely rewarding.
  • Previous side projects that I enjoyed were creating websites, and web based tools (like TweetSeeker) although I never really made any money off them. TweetSeeker was a work in progress related to a research project that got shelved. Since then, as no one else seems to use it, I just can’t get motivated to advance it.
• This is to be thought of as a 20% time project (mostly Saturdays, or slow Sundays)

So if anyone else has some ideas, or questions that might help me narrow it down, I’d love the feedback. Comments, or emails are greatly appreciated.

As I mentioned before, I’ll write about the side project as it unfolds, and I’ll tag it as “Side Project” for easy finding.

Continue reading »]]> Earlier this week, I heard about Googles latest social offering. After checking out all the videos and information about the Google+ Project online, I was eager to hop in and try it out. I quickly put my name in for an invite, and the. I waited. And when I got tired of waiting (a few hours, pretty sad), I started looking for people that had invites. I think it was the next day that I found a friend on Facebook had some, and I quickly leaped at the opportunity.

For the last few days, I’ve been using Google+, and I can quickly see the potential for this to become my member one social network. Hangouts are pretty awesome, and though I’ve only used this a little, I could see the potential for this to replace Skype plus. One of the biggest sells to be though was the ability to select groups of friend with whom I could share content. This made some much sense to me, that it wasn’t until this morning that I found a problem with it.

It wasn’t a huge problem, it just caught me a little off guard at first. When you first post some content on Google+ you select a group that you want to share it with. For example my wife shared a few photos from a recent trip that we took. I thought these were pretty cool, and I might want to share them with my colleagues. To my surprise, I did. It was kind of odd really, it seemed clearly like a bug. But after checking the help dialogs, I found that this was in fact intentional. You could on the other hand disable sharing on a post by post basis.

A friend of mine brought up a good point. Enough if you were to disable the ability to share a post, picture or otherwise, they could just as easily screenshot it and share the screenshot, or just telling others what you said.

This is where I believe the basis of any true trustworthy sharing should come in.

You should never share anything with someone who, knowing your wishes, you can not trust to abstain from sharing beyond those wishes.

But what if someone didn’t know it wasn’t ok to share with others? Can they really be to blame? Of course not. Although we can all believe in common sense, there are situations where a user might feel that certain content is worth sharing, but doesn’t realize this is ok. But setting every post to disable sharing can be very tedious.

But what if there were a better way? You probably have social circles which which you would be more comfortable sharing more personal details than you would with other groups. These personal details you likely wouldnt want being shared. So why not be able to set the sharing defaults based on your circles?

Although it can’t replace the trust rule above, it can augment it. The sharing link would then act as a flag or a signal to your circles. Share link is there would mean “feel free to share this”, and no share link would imply “please respect my wishes and not share this”.

This is just my idea for what could make Circles on Google+ even more useful, but I would love feedback.

Continue reading »]]> Gargi Bougie, Jamie Starke, Margaret-Anne Storey and Daniel German. In Proceedings of the 2nd International Workshop on Web 2.0 for Software Engineering. 2011. PDF of the Paper | DOI Link | ACM Link
© ACM, 2011. This is the author’s version of the work. It is posted here by permission of ACM for your personal use. Not for redistribution. To appear in Proceedings of the 2nd International Workshop on Web 2.0 for Software Engineering

There has been some research conducted around the motivation for the use of Twitter and the value brought by micro-blogging tools to individuals and business environments. This paper builds on our understanding of how the phenomenon affects the population which birthed the technology: Software Engineers. We find that the Software Engineering community extensively leverages Twitter’s capabilities for conversation and information sharing and that use of the tool is notably different between distinct Software Engineering groups. Our work exposes topics for future research and outlines some of the challenges in exploring this type of data.

http://www.wordle.net/ overview of the paper:

Continue reading »]]> For anyone that checks my site regularly, I’m sure you’ve noticed some fairly big changes over the last day or so.

I recently decided to move to WordPress, over my old Drupal site. There were many reasons for this. Drupal is an immensely powerful CMS, but with great power, comes great responsibility. Specifically, I found that there were frequently critical updates that were required for my Drupal installation, and it was my responsibility to take care of them. This involved downloading the latest versions of the Drupal core and any modules, going on to my home laptop, opening Cyberduck (ftp), connecting to the server, backing up my database, putting the site in maintenance mode, uploading the new versions of any modules, then running the database upgrade scripts. If it sounds like a lot of work, believe me, it is.

Even after all that work, I was never really happy with my installation. It always felt like it was slow, and people would comment that my site is slow. I was constantly looking into ways to speed it up, and eventually I came to the realization that I was putting more time into maintaining my Drupal installation than I was putting into adding new content to my site. If you ever find yourself doing this, run…

I started to look into alternatives. I had worked with WordPress before and it seemed to work well, but I figured I would check to see if anyone else had recommendations. I sent out a tweet, and only received 1 response.  Christoph told me that he had been using WordPress for a while and it had “Practically no maintenance effort”.  That was just the nudge I needed (thanks Christoph). To my surprise, many things are so easy on WordPress, that I was able to even install a number of Plugins I needed, from my iPhone!

So all my content is now up on the new site, although the urls have all changed (ya, WordPress takes care of that, on Drupal I did it mostly myself, but I know, it too could be automated on Drupal). So, welcome to my new home online.  I hope that you find everything you’re looking for.  If not, let me know (contact info on the right side), and I’ll do my best to fix it up.