Open Source Tooling : Deploying to Heroku

Heroku is a tool available to try for free at . It allows for developers to put up server code that they can then share with anyone. This is an extremely useful tool when it comes to working in the open source community and sharing projects with team mates and friends. All you need to do in order to get started is create an account, and install the CLI application to allow heroku to automatically sync with your git repo.

When I first tried it I extended the code I wrote in the last lab to be able to be ran on express server. Express allows you to easily make your JS code accessible with a server. To merge the express server and heroku cloud service, we have to add a couple of things to our code. One of them is a file named Procfile, all it contains is information on what server we want to use, in this case it’s web: node server.js.

Once everything is set up and running you simply push your git changes to the automatically created heroku git repo. Once its up it would be running on the web with the url it provided. You can check out my server at :

This is what it looks like when passing some parameters to trigger a function, for example healthcheck :


Overall this was a great lab and it taught me an easy way for me to code a server and share it with people I am working with. If you ever think you may need to do some simple servers or test code for your application and want to share it online, check out Heroku! Only takes about 10 min to learn. That’s it for today, have a great one.


OSD600 Lab 8 – Unit Testing

For Lab 8 we got a chance to create a java script testing program that automatically runs when we run our builds on Travis. It is quite easy with the technology from facebook to allow us to code our tests for specific function and easily test them against multiple tests to see what passes and what fails.


As you can see it’s very easy to create a test function for the function. And this file after it’s pushed gets ran by Travis which allows us easily to tell if any of the above tests have failed.

Unit testing is a new topic for me and I found it very interesting. It allows for an interesting approach with developing with test cases. to be honest I did not find anything hard about this. If anything it is much harder to do this without knowing how to create proper tests for your functions.

I will try to take the approach of test oriented development in my future javascript projects as it seems to be a good way to develop small and large applications that require precise handling of data.

You can check my build on travis using this link :

SPO600 optimizing GLIBC function “strcspn”

I choose to optimize the string library function strcspn because it looked like it could use some cleaning up at the very least. First to explain what the function does. STRCSPN take two strings and compares the first string against any of the characters in the second string. Ones a matching character is found, it returns the number of characters in the first string before the matched character. For example string one will be “test1” string two is “1”, the function will return 4, as 4 characters come before the first matched character. Now lets take a look at the current implementation of the function.


It’s a little bit confusing but from I understand, it uses a table and tries to find the matching character at which point it starts calculating the number of characters to return. So far I’ve come up with a few different implementations, mostly getting around 1.5 – 2% increased performance. The implementation I am currently testing is very simple :


All we are doing here is looping through the first string and using the bit operator ^ XOR to see if any bits match between the two strings, counting our return value up when we don’t find a match. So far with my testing this function works properly and is about 2% in terms of improvement. Looking to see what I can do to it further to increase either performance or memory.

OSD600 Release 0.2 – Small fixes and adjustments

For this topic I choose two issues to work on :

However I wasn’t able to replicate the issue in 1728. I believe that has something to do with specific system configuration. When I tested on my machine I was able to have it working. So unfortunately was unable to help with that issue. However I feel like it may be better for someone with that issue to have a go at it, as it will be easier to test.

For issue-619 I did simple adjustments to the console logging that was present in some of the LiveDevelopment files. To summarize the changes :

remove console.log(delta);
remove console.log(“Edits applied to browser were:”);
remove console.log(JSON.stringify(result.edits, null, 2));

remove console.log(“You must connect to the WebSocket before sending messages.”);

console.log(“Invalid launcher object: “, launcher, new Error(“LiveDevMultiBrowser.setLauncher()”));

remove console.log(“Edits applied to browser were:”);
remove console.log(JSON.stringify(result.edits, null, 2));
console.log(“[Brackets LiveDev] Received message without method.”);

console.log(“[Brackets LiveDev] Error executing a handler for ” + msg.method);

remove console.log(“[Brackets LiveDev] No subscribers for message ” + msg.method);

console.log(“[Brackets LiveDev] Trying to send a response for a message with no ID”);

remove console.log(“Runtime.evaluate”);

console.log(“[Brackets LiveDev] Malformed message received: “, msgStr);

With current production version there are some that ran way too often like the Runtime.evalute log which ran every action look below :


This may be fine for a desktop version of the application where console is unseen, but for browser it fills it up with unnecessary waste and can cause it harder to debug. Nevertheless I removed those logs that I thought were being unnecessary, and kept those that are useful in terms of debugging an actual error handling function.

There is one more issue I kept track on, trying to figure out, but didn’t have enough time to. I am still looking at the side, and may want to ask for help for it, as it has thing I don’t really understand how they operate. The issue in question is :

It may need some discussion as it alters a functionality currently in the editor. But the solution does look promising as it makes it more friendly for the user to use.

I wish I had some more time to work on this release, but I had some issue during break week that needed to be handled. Will try to go for a big bug/ feature for next release thought!



OSD600 Lab 6 – Editor Comparison

For this lab I have decided to compare two popular code editors, Atom and Sublime text. Now to let you know right away I have not used atom ever, so it was more of a first impression kind of thing. Sublime on the other hand I have used but not have dived deeply into the customization and preferences of the editor. Here is what Atom looks like with Brackets opened :


Now I will show how to configure some of the features of the editor. First up lets try to search for a string in a file and then in the whole project.


As you can see finding things is rather simple in Atom, and the interface is not that bad when searching the entire project.

Next up to install additional extensions, all you simply need to do is Click Packages -> Setting View -> Install packages


Some common key binds you will find in the editor :

  • CTRL – F ( Search inside the file )
  • CTRL – SHIFT – F ( Search inside the project )
  • CTRL – L ( Select Line )
  • CTRL – SHIFT – +  (  Increase Font Size )
  • CTRL – SHIFT – –  ( Decrease Font Size )

There are many more key binds simply by looking around the top menu you will find lots of more useful binds you can use.

Next lets have a look on how to split the view.


Extensions – There are plenty of extensions for Atom, ranging from a variety of things such as auto text complete to simplified usage. The following extensions I loved the most :

  • Atom Beautify ( Cleans up javascript code to look nicer, and stylizing it so everything looks the same )
  • autocomplete-clang ( This is a autocomplete for C/C++, as many of my code is written in those languages, it is awesome for writing quicker and easier)
  • git-plus ( this allows for git control without using the command line interface inside atom)

Here is a look at how some of them function :

Beautify :




Thanks for reading, how you find an editor that is good enough for you :).