Fixing bugs in vscode

    For Lab 3, our task was to tackle an issue/bug with vscode.  While tackling bugs one of the first things we had to accomplish was to recreate the bug on our machines.  Initially this seemed like a very easy task, follow the steps mentioned in the issue to create the bug and BAM! you got something to work with right? NO.  This was never the case with us.  We tackled the issues listed on the wiki page and wasn't able to recreate most of them.
   We tried the colour picker issue #42720, this seemed like it was a fixed issue.  I wasn't able to recreate it on my Linux system and we also tried to create it on a Windows system with no success.  Then we tried the Opening .bat files issue #43302, this was also a fail as we couldn't get the issue to come up.  Then finally giving up on the list provided we ventured out into the 4000+ issues listed on the vscode GitHub.  We filtered for the labels good first issue and bug and found one that we decided to tackle.  We decided to tackle issue #36219 "Stage selected ranges" command changes encoding to UTF-8 (without regarding to the initial file encoding).  There was video file on the issue page which showed us instructions on how to create the bug exactly which we followed and ALAS! we were able to recreate the bug.  This was on my friends computer so, he tried to screen share it with me and tried to do it again, and our bad luck struck again and wasn't able to recreate this issue.
   This shows how for issues to be recreated there are certain criteria to be met.  Maybe the person who encountered it had a superior system and ours was not that great, there could be millions of reasons.  Although finding an issue to fix was not the easiest thing to do, I will keep searching for that one issue that has eluded me and I will have my first issue fix on Microsoft's vscode.

Comments

Post a Comment

Popular posts from this blog

Assignment 1 - DPS909

   For this assignment, our task was to use Google's libphonenumber library and create a RESTful api web service which would get the phone numbers from a string that is provided and also from a file that is provided.  The initial task was to determine what language we want to use to achieve the final result.  For me, I went with JavaScript, as I have worked with JavaScript before and would require less effort to achieve the result.  So for this assignment I used Node.js which is a JavaScript run-time environment which allows the execution of JavaScript code on the server-side. Dependencies used with Node.js express google-libphonenumber multer body-parser mocha chai chai-http nodemon     Express is a framework that allows the creation of web applications for Node.js.  This specific framework is the most standard framework for Node.js, which helped in making the decision rather simple.  I also used the google-libphonenumber package which uses the original libphone
Read more

ECMA Script Testing

Image
For this lab we looked at the ECMAscript test suite. Setting it up and making it run was fairly simple and I didn't encounter any issues.  I just followed the steps provided in https://github.com/bterlson/test262-harness#test262-harness While running the tests not all of them pass. I thought this might have been a Windows issue. Therefore I tried it on my Linux machine and majority of it worked except 6. Then we looked at the test cases for Array.prototype.reverse().  For the task of this lab I simply just rewrote some new test cases to check the array.reverse.  This was fairly simple as looking at the other test cases it gave a general idea on how to write test cases for this. The test case I wrote can be found here. https://gist.github.com/pranoy10/10fd4bbf04a7490567d527017c8d52df
Read more

Release 0.2 - Bug fix

   The bug I decided to fix for this release was a very quick and easy one.  It was to update the show more button.  It can be found here . It is not really a bug but it was a minor change that they wanted. Using devtools in the VSCode, it was very easy to figure out which file was the one that needed the change. It was in the  src/components/SecondaryPanes/CommandBar.css . The Line was changed to: mask : url ( / mc/command-chevron .svg ) no-repeat ; Since this was a fairly simple bug to fix, I went ahead and decided to learn more about how the project structure is. This would help me tremendously since I plan on working on the same project for the next release.
Read more