Http-Parser: my first open source project

Starting...

Over the past 2weeks, I have been trying to implement command-line tool for finding and reporting dead links (e.g., broken URLs) in a file. Although I had a bit of struggle at the beginning, I was able to get in track by checking Slack communication and asking professor. What I have learned from this release 0.1, is how I can start open source project. I was not comfortable since there is no strict instruction, also, it was open choice which language I like to work on. I just started to implement the http parser with node.js.

After 1st push...

After I implemented the application, I realized the performance seems really slow. Thus, I post question on slack and the professor suggested solution via git. It was actually first time for me that anyone was looking at my git, fix, and pull request. It was great experience that I could see all changes were applied to my master once I clicked the button.

Ex)

First code look like:

Fixing code:

Of course, there are also more changes to restrict method to header and timeout not to spend a lot of time.

Make it better

Today, I have great experience by browsing others git repositories since they chose different coding style and libraries and there are some I had thought about. To be honest, I am still very careful that I create an issue or contribute some because my task or view may be wrong or maybe I have some concern about judgement. Anyway, today I contribute to create issues on other's repository and even my one.

During this parts, I have learned what is label, what is milestone and what is project which are just awesome!

Conclusion

I was really considering if I should drop this course because I had no idea and there is no clear goal even though it was only for me. However, instead of keep silence, I tried to ask a lot about my concern and my professor said I am on right way so now I am very happy for taking this course although still I am not confident LOL.

Comments

Getting more difficult?

Release 0.2.4 Now I am at almost the end of release 0.2 and I chose the telescope as the final contribution. To be honest, this is huge, well organized and great project and it is first time to take a look. Unlike my previous assignment during the previous terms, there are tons of what I have never seen. First, docker compose is great and the document for contribution is very clear. Of course, I had no idea when read it first, but every time as my professor mentioned, there was a great guy, helper?, helping me a lot to set up the project. Although I had no idea about Elastic-search and Redis-cache server, I was happy to take a time to look though the codes and to understand. Again, trying to understand an issue is always hard for me and sometimes I am really not happy when somebody does not understand my question. This happened again. The reason why I attached the picture is that I am still confused about the whole process of this project especially about why frontend didn't get ...

Finally, release my first open source.

Starting... This lab is to release my product to install easily. Instead of cloning or downloading and setting it up manually, it provides a lot of convenience for users to install it. I chose NPM since I used nodejs. NPM is a great site to help develpers to release their git repository in the site. Progressing... First, I signed up on npmjs.com and logged in the site on the console to release my repository. I had to set up a lot of things like 'npm init', modifying readme and package.json to be ready. Second, I tried to release my repository by the command, 'npm publish --access public'. Unfortunately, the name, http-parser, was already taken, so I needed to change my name. I chose my name as http-checker and tried to release it again. At this time, I got 403, forbidden error. I spent a lot of time to figure out but it was actually due to not verified account. Once I got the verified email account, finally, I got the release version of my repository. Here is my...

Elastic search and more

Release 0.3.1 Now it is time to learn what is Elastic search since the chosen issue is about adding more fields for our model in telescope. This is very new for me so I was very scared when I started to work for this but now I think I am more confident. First, Elastic search is such a great supportive database especially for index search. The good thing is that it is not only the index search for whole value but, partial keyword as well. Of course, it may be wrong since I also just started to study it. Anyway, It was very careful when I read codes one line by one. Following the official document , I tried to add some fields, but it made some test failed so I needed to fix them. The below content is from the official document: Mapping edit Mapping is the process of defining how a document, and the fields it contains, are stored and indexed. For instance, use mappings to define: which string fields should be treated as full text fields. which fields contain numbers, dat...

Stella's Blog

Search This Blog