Bug Release 0.2 Update

Hello Again as i previously stated in my introduction for Release 2.0  my confident was shattered going in to this project. but after spending some Time to properly research the bug before i ask to be assigned. i was very confident that i had the ability to solve this bug. the issues in question needed to Styled console logs with unit-less line-height default to px unit. this seems to only affect the new Mozilla fronted even though the server was returning the correct style


after consulting with my professor.he took to time to help me get up to speed with some java-script that might help me to solve this bug. both my professor and hi was amazed at how the developers was using the bowers to perform some cool debugging. my first approach to this was to leave the code as is,but create a function that would perform some clean up before it reaches the dictionary


The developers suggested that i should create a dictionary with key “line-height” that can also be checked by the browser, but this would seem costly as it would call for more files to be edited.




this define a stub aka JSON objects, and because it was modified it will also needed to updated. i also had to make sure that the browser was able to check if lineHeight style is 1.5 and not 1.5px.


the bug was successfully push for review and is awaiting approval.




Testing Python with Travis CI

Continuous integration is an important part of software development and has Many advantages, such as a faster development cycle, And higher software quality. Travis CI is a service that provides continuous integration and will test your software project for every change. Their service provides testing environments for many programming languages including C, C++, C#, Java, PHP, Python, Ruby, and just to name a few.

To Get Started with Travis Ci, You must Allow Travis To know about your GitHub public projects. Login to Travis CI and press the “+” button. Next, flick the repository switch on for your repo.


at First i did not see any of my repositories, but after i hit the sync button to refresh the list of public repositories.

Next is to create  a .Travis.yml File in the root of The project repo to start a build configuration. This can vary from language to language and even if your project is using the command line.


  • The ‘language’ section is used to specify the language of the software.
  • The ‘python’ section is used to specify the version or versions of Python to use for testing.
  • The ‘script’ section is used to specify the command to test your software. Typically, this command will find all tests in your project and run them. The specified command must exit with a status code of 0 if the test is successful; otherwise the test will be considered a failure.


Lastly is The Process of Triggering The Build. the step is very easy just push the commit that adds “.travis.yml” to the project, and Travis will get to work


Mozilla first Bug

the  plan for my first bug fix “0.1 release” was to play to my strengths.  i wanted to work on bugz that affected languages such as c++,java or python with the hopes of learning some real world problem solving that can be applied to my resume. a good portion of the bugs that a listed under “Good first bug” seem to be aimed at more front end languages like java script, css and so on. this issues made landing a bug a bit tricky. it took me two weeks to land my first bug. the bug that i landed was css base and was asking to Remove the dotted focus border from selected row. this one seem very simply at first. the instruction was straight forward.

  1. clone Mozilla central
  2. build the repo
  3. use yarn to inspect what was causing the issues

using yarn to find the issue took some time, and some assistance from my professor. we decide to apply “outline: none !important” to the request-list-item .after submitting the patch i was old that by using “outline: none !important” would cause future problem when debugging the css, and  should look into using “:-moz-focusring”. after doing some more research i  finally fix the problem, and proceed with submitting the final patch. after my submission a users pointed out that by removing the dotted line might cause a break in the keyboard accessibility. after this they decided that it would be best to leave the bug as it is  so we won’t break the keyboard navigation. i was very disappointed with this decision, but was happy that i made some progress

creating a github Library

for this week lab we was instructed to create a simple library that can perform some simple task, such as calculate different hash codes,read file size, and display file name with out the path. this task was to be performed by using one of five Language. JavaScript (or TypeScript) and node.js, Python, Rust, Go, or Swift; i descended on going  with python because of its growing in popularity. getting started with python was fairly easy; the syntax makes it easy to write and not hard to read,but difficult to analyze. i was able to find some open source python code that i can re use,but decided to try and implement them my self so i can get some better understanding of how python works. the second part of this task was to create a git-repo with the appropriate License,and a well documented read me file instruction on how someone can  use or make changes to the library.

we were also  ask to contribute to someone else library, but at this time i have not yet gotten the chance to do so.