Release 0.4 #3 - Release

Introduction

This is the last blog to my release 0.4 for OSD600. I was not overly ambitious as my previous releases in order to set myself to succeed.  This post will be on what I have completed and what I tried doing.

Implementation

 For my main issues for AOC repository, I completed days one to five as expected and also day seven is done but I did not push my code yet.  I will do so at the end of the week to give others a chance to come up with the solution.  What gave me most trouble was day six, because if you do not setup the program correctly in order to do exponential growth of input, you will run out of memory.  I thought of using hash tables to instead allocating blocks of memory to over come this problem, but have yet to written it properly in python.  Days three and four took the longest time because i had to review my data science knowledge.

The following is my progression up to day seven to represent the week of work I did.

 

As mentioned in my previous posts, I finished the changes for my translation as per request by reviewer.

The following is the running website image of my pull request for the prompts-ai repository.

 

 Unfortunately I did not dive far enough in the Telescope issues and they are not completed for release 0.4.  I will look into working more with open source projects in the future as the new year begins soon.  Things that I would have done differently is look at more issues on Github to get a better grasp of the things ahead as I did not know I will be continuously looking for issues during the course of this semester.

God Bless,

Eugene Chung

Release 0.4 #2 - Progress and Backup

This week I switched gears and plans for release 0.4.  I found I am inadequate with finishing the three Telescope issues and made a backup in case I am unable to solve them in time.  My backup for my main issue is participating in Advent of Code and learning and coding in python while starting out the first five days of the programming challenge for December.  I feel this is truely open source if I share my experience of how to solve some of the beginning issues so that others may see how it can be done.  I have marked the issues for my repository as #1, #2, #3, #4 and #5 for each  of the five days.  I feel I am more confident in finishing this task rather than struggling with Telescope.  I am not dropping the Telescope issues yet, but I need to finish tasks where I can be allocated some marks rather than none.

Open issues have dried up significantly since Hacktoberfest, but I would like to address my previous issues that I made a pull request but did not merged by author.  One of these issues, is the Chinese chess repository the author has kindly responded and I made the corresponding changes.  Another is a pull request where the author has not responded, but I made a test Vercel website to verify that everything works at this link.  I did this because our professor mentioned in a comment during release 0.3, that he wants me to finish issues.  Thus when I have extra time I will also look into the Telescope issues.

On the note about Advent of Code it is very interesting, there is a recurring theme on each of the Days of the code and you only input an answer for each of the Days of the month.  For those who doesn't know you can have a private score board and people try and compete with each other for points and stars.  You get one star for each question completed and two for the day if you also complete the challenge part 2 for the day.  I want to thank my Algorithms professor Catherine for the idea and showing the event to us.  I feel like my ability to write better python code or any other language stretched to its limits as each day, presents a new challenge.  I made progress by finishing pull #6 and will finish the rest by end of this week.

I am also busy studying for finals like everyone else this week.

Kind Regards,

Eugene Chung

Release 0.4 #1 Disaster management

Introduction

I believe at the start of the week I reset my computer, however as I tried to create a recovery drive I accidentally wiped the wrong drive which is my main backup.  Long story shot a lot of data was lost and time to reset everything.  That was last week.  I'll be real honest with this post and life happens not the way you intend, but there is hope.

 The Issues

I was only able to select a Secondary issue on IPC144 to continue my search from release 0.3.  In addition, I have to start over with the search issue and I have yet to begin looking at viable solutions due to pressure from my other courses.  Sometimes students need to be pushed to their limits in order to simulate real world scenarios where deadlines are not met in time.  The beauty of open source is that it can be picked up quickly and not all is lost as long as I push through in the end.  However this maybe another big task as I thought i was suppose to finish my previous work which is now scrapped.

As for my main issue is a combination of three issues from Telescope.  It is maintenance work on updating logger to use printing API in pino.  The relating issue is removing all elastic APM code from telescope  and update pino to make sure everything works.  I probably need a lot of help with these issues as I  have no idea how they work because they may seem trivial as a logger tool in Telescope.

Overall my motivation at the moment is low and I am sure there are many low points for everyone.  Hopefully I find the strength to push forward with these issues in the end and manage studying for my exams with my other courses. 

Kind Regards,

Eugene Chung

Lab 10: Software Release

 Introduction

This week we are looking at software releases and getting our code into the hands of users.  We are working with git tags, package managers and user testing.

Step 1: 

I am using Node.js so I picked NPM as my release method as suggested.

Step 2: Implementation

The only tricky part of this lab is needing the --access public in order to publish the package publicly.  This is the only part that I got stuck and needed to search on Google.

Other things such as having the correct version number for each iteration of release in package.json and making sure the package installs locally and works as intended.

Step 3: Tagging Releases

 This is relatively straight forward.  I created tags on main and used git to push --follow-tags.

Step 4: Do A Release

My release is located at https://www.npmjs.com/package/@ycechung/cmd-ssg, and I finalized on version 1.0.2.

Step 5/6: Update Documentation

I made sure my documentation is updated and pushed on Github.  In addition, I made sure others know about my release and tested installing my project using npx.

It is near the end. Labs are done.

Thanks for Reading,

Eugene Chung