Articles on hanslett12's Blog

WEEKLY BLOG POST #15- GSOC Week 18 to week week 21

hanslettthedev@gmail.com (hanslett12) — Mon, 23 Oct 2023 11:38:54 +0000

In summary, I have not been able to post updates about my progress because I totally forgot I was suppose to post though I received an extension.

I had 4 of my pull requests merged during this period and I have 3 opened. The three remaining pull request opened are for writing unit test cases for pyafipws.

My evaluation period is drawing close, so getting those 3 pull requests merged will surely put an end to my GSOC Journey

WEEKLY BLOG POST #18-> #19 GSOC Week 17 and 18

hanslettthedev@gmail.com (hanslett12) — Sun, 01 Oct 2023 23:46:23 +0000

Hello there

Right now, I am working on the following PR's here. And I will give a brief summary on each one. The major PR is the one which involves deploying the packages to PyPi. Now the interesting thing about this one is it's merged but I have to add some testing support. The next one involves preperaing unit tests so that the can be used to test some modules that don't have test coverages. And lastly, the PR that manages the module setup.py build process and fixing dependency requirements.

I hope to get them merged by the end of the week

WEEKLY BLOG POST #17- GSOC Week 17

hanslettthedev@gmail.com (hanslett12) — Sun, 17 Sep 2023 23:20:32 +0000

Hey!
This week,I didn't do much since I was preparing drafts to work on a huge PR to deploya test to PYPI. and I totally missed my schedule for last week so Seems I have to cover up this week

See ya

WEEKLY BLOG POST #15- GSOC Week 15

hanslettthedev@gmail.com (hanslett12) — Mon, 04 Sep 2023 20:39:20 +0000

Hello there

This week I was doing more of some research work while trying to come up with some innovative ways to solve a certain problem I encountered while working on this pull request. Now let me give a brief explanation of what the problem is.

WHAT DID I RESEARCH ON THIS WEEK?

The problem: Now I am working with a python package which will soon be deployed to Pypi. But the project has dependencies like every other python project out there. And If I want PyAfipWs to be installed with the same packages as we use in the development phase, we have to freeze the requirements.txt. But our project uses setup.py and it has a key word called install_requires which indicates which dependencies are required for the project to run smoothly. Now what the requirements.txt those is it freezes core packages but it doesn't explicitly declare what dependency versions that are used by the core packages are actually stable with our current code for PyAfipWs. Now here are some constraints that guide how the dependecy pinning should work

packages version should be relaxed (>= or ~) to avoid diamond dependency issue (avoid conflicts or forcing other project with our versions)
we should test latest versions this instead the pinned dependencies in the requirements.txt
we would need to use pip-tools or similar to freeze requirements.txt

There are many ways to solve it. One way is to manually specify the dependencies that will be used. While this is good but in the long run becomes hard to maintain. Pip-tools is a great module as it integrates directly with pip itself. We can use it to generate a requirements-dependencies.txt from a requirements.in file and create GH action that can automatically generate the new requirements.txt file and then read the file from the setup.py file so it always has the pinned versions like we had in our development environment.

WHAT I PLAN DOING THIS WEEK?

Implementing the above solution and working with my mentors to ensure it works well and then proceed to setting up the deployment to PyPi

Until next week, see ya

WEEKLY BLOG POST #14- GSOC Week 14

hanslettthedev@gmail.com (hanslett12) — Sun, 03 Sep 2023 19:46:39 +0000

Hey!
This week, Has been a bit tough on my side as I had some personal issues to solve so I wasn't able to work well. This explains the reason why I am making my blog post this late.

But I was able to get 3 pull requests merged #136, #131, #125. Yes and I am happy to say I am almost close to completing my project proposal for GSOC and I am looking forward to completing the GH action for deploying to PyPi

WEEKLY BLOG POST #13- GSOC Week 13

hanslettthedev@gmail.com (hanslett12) — Sat, 26 Aug 2023 11:35:08 +0000

WHAT DID I DO THIS WEEK?

This week, I was doing lot's of research on some issues regarding the python 32bit and 64bit build. Interesting to know that in the requirements.txt file, you can not specify if the host computer is a 64bit or 32bit. Though it provides some useful enviromental markers like sys_platform, they all return win32. So right now, I am working in collaboration with my mentors on a workaround. I came up with a solution which works but still waiting for feedback from my mentors. Secondly, I have 3 pull requests open #133, #132, #125, #127 that are on the verge of being merged

WHAT I PLAN TO DO THIS WEEK?

I plan to get these pull requests #133, #132, #125, #127 merged by the end of the week and also start working on the final phase of my proposal, which is the automatic deployment to PyPi via GH actions

WEEKLY BLOG POST #12- GSOC Week 12

hanslettthedev@gmail.com (hanslett12) — Sat, 19 Aug 2023 13:52:00 +0000

Hello there
Well I'm happy to say I'm recovering steadily and looking forward to working on my GSOC time. Last week, I made a request to get an extension due to poor health. And my gladly, my extension was accepted

WHAT DID I DO THIS WEEK?

This week, I was able to complete and merge a pull request. This means in total I have 4 pull requests merged at the time of writing. This is good improvement but much work still needs to be done. I was able to go 80% of the next draft pull request which entails modifying the existing github action to push a release update everytime a pull request is merged to the master branch. Currently it releases it only as a release artifact but not deployed as a release in the github section. The aim is to get it ready by the end of this week.

WHAT I PLAN THIS WEEK?

My plan this week is to continue on the draft proposal and start planning how to create another actions feature to deploy test coverages as release artifacts in the GH actions. And more to that to continue to write the left over unit tests that are remaining for some modules that don't have any test coverage.

WEEKLY BLOG POST #11- GSOC Week 11

hanslettthedev@gmail.com (hanslett12) — Thu, 10 Aug 2023 15:31:11 +0000

NO UPDATES THIS WEEK

Due to poor health, I have not been able to work this week. I was discharged from the hospital this week and still recovering, I have requested also for an extension`so that I can catch up properly

WEEKLY BLOG POST #10- GSOC Week 10

hanslettthedev@gmail.com (hanslett12) — Fri, 04 Aug 2023 09:19:37 +0000

NO UPDATES THIS WEEK

Due to poor health, I have not been able to work this week. So I will resume only from next week. Thanks

WEEKLY BLOG POST #9- GSOC Week 9

hanslettthedev@gmail.com (hanslett12) — Wed, 26 Jul 2023 06:59:45 +0000

WHAT DID I DO THIS WEEK?

To be honest, this week, I didn't make the needed progress as I would have expected. This week, I opened 3 pull requests, one was a pull request draft for writing unit tests on a certain patch I provided for another pull request and currently now it needs some end to end testing. But the bad part about this was I didn't have lots of experience writing unit tests. So the whole concept was a bit confusing and I have to use lots of advanced functionalities using pytest. This has led me to the thought that i might need to ask for an extension If I can't deliver as required. Secondly I have another daunting task which was to write some unit tests again for another issue related to the overall performance of the web services. And due to the difference in time zones between my mentors, communication is not 100% fluid. It could help if the responses were a bit faster. But I have myself to blamed partly as I have not been up to the gear.

WHAT I PLAN DOING THIS WEEK>>>>>

I'm sure it's obvious. I want to improve. I want to be able to get those 3 pull requests ready this week. Else I will be requiring an extension. So I hope to give a positive feedback about the 3 pull requests and merging them. So I can be in sync with the deadline and prepare for the final evaluation.

WEEKLY BLOG POST #8- GSOC Week 8

hanslettthedev@gmail.com (hanslett12) — Thu, 20 Jul 2023 21:59:32 +0000

Oh yes If you're seeing this post, it means I have successfully passed my midterm evaluation and looking forward to the final evaluation

WHAT HAPPENED THIS WEEK?

Well I passed the evaluation and I got some tips from my mentors on where to improve. I'm grateful they passed me.

WHAT I PLAN DOING NEXT WEEK?
Continue working on achieving an automatic Github Actions release and write some unit tests for some issues in the REPO. As you noticed this week, I didn't do much but the passing of the evaluation sums it all and I look forward to getting things done a bit faster

Sorry for posting late though
Until then see ya

WEEKLY BLOG POST #7- GSOC Week 7

hanslettthedev@gmail.com (hanslett12) — Fri, 14 Jul 2023 00:22:56 +0000

It's the GSOC Evaluation Week and it's during this period your fate on the GSOC program lies in the balance of your mentors. They have the final say to show if a contributor is serious or worth the stipend. For sure, I will not want to miss on the opportunity so this week was a crucial one. So enough with the waffling and back to business.

WHAT DID I ACCOMPLISH THIS WEEK?

Simply put, I didn't do anything significant this week, other from the part I was reading on unit tests and practicing since I have to write a bunch of them at the fall of the evaluation period and beyond. It's 6 weeks already, and I can say I'm on track to completing the core issues needed so I can work on the main module to deploy products automatically on PyPI via Github Actions. Hopefully I get to share some great news after the evaluation period as it's very crucial too

WHAT I LOOK FORWARD TO THE COMING WEEK!

Writing lot's of unit tests, Opening pull requests, getting feedback and corrections from mentors and getting them merged. That's why I'm here in the first place! To improve on myself and the github organization services. Hopefully I'll be able to hit the jackpot and continue with the same zeal regardless of the outcome,
Until then See yaaaaa

WEEKLY BLOG POST #6- GSOC Week 6

hanslettthedev@gmail.com (hanslett12) — Fri, 07 Jul 2023 05:25:25 +0000

Hello there, It's week 6, And unfortunately, I really do not have too much to say because I'm not feeling too well. I was diagnosed with malaria and I'm still undergoing treatment. But all I can indicate currently now is that I'm recovering and I had a pull request merged.

What did I do this week?

Due to my poor health this week, I wasn't able to proceed normally as I would. But gratefully I'm recovering. The only thing I am sure of that boosted me was having my pull requests merged this week. By next week, I'll be fine by God's grace so that I can proceed with my proposal workflow

What I plan doing next week?

I thank all of my mentors who have patiently been helping me to make the necessary changes. And I've learned a lot from them. They already suggested this week I should split a certain function and then write unit tests. That is my job next week before the evaluation period begins. Until then, ciao

WEEKLY BLOG POST #5- GSOC Week 5

hanslettthedev@gmail.com (hanslett12) — Mon, 26 Jun 2023 21:49:15 +0000

Oh well, It's your boy Hanslett again with another GSOC blog post. This week was full of ups and downs but I would say it was a good week. Here is a small recap of what I'll be sharing today

RECAP FOR THE WEEK

1. Server failure and deprecation of python 2.7

In python Argentina's official repository, there is a python 2.7 test that runs in our Github actions that is required to test some web services running on python 2.7. Unfortunately, Github officially deprecated the support for python 2,7. And this has pushed the owners of the projects to reconsider supporting python 2.7. While the builds for python 2.7 was failing, another crucial web server failed. The web server in charge to host the digital certificates. It also contained the certificates used for testing the overall functionality. With the failure from this web server, it means the overall testing functionality for the whole project failed. And this slowed down the overall progress of some of the PR's I was working on

2. Creating new PR's

Yes, you read that right! Creating a new PR was an issue. Week 3, I mentioned I was working on a draft PR that solved about 2 issues. But my mentors insisted I separate my new PR's into their separate PR so It can easily be tracked. This wasn't easy as I had already squashed most of the commits. And I was advised to use max 3 commits per PR to make things look cleaner. This particular step helped me appreciate what it means to actually make a good PR. Good PR's are not about the number of commits, it's rather about how organized and simple the commits are. Making a minor change like fixing an indentation is a commit which has no significant improvement to the overall structure. This is a lesson I learned from one of my mentors!

There's much to say about this week, but I might Cap a lot and spoil the fun for next week. So just chill and wait for me next week for more details!!! Until then, See ya

WEEKLY BLOG POST #4- GSOC Week 4

hanslettthedev@gmail.com (hanslett12) — Mon, 19 Jun 2023 07:55:23 +0000

Hello guys, it's another week, and finally, things went in the right direction. Last week, I was frustrated with the number of bugs that kept popping up while trying to prepare my draft PR. But this week, Thanks to the great help from my mentors, I was able to resolve all those bugs and made significant progress. Let me share a brief story about what happened.

WHAT WAS DONE THIS WEEK?

So here is a detail description of what I was trying to solve. PyAfipWs signs digital certificates for their web services. Now the module has some legacy code for backward compatibility for lower versions of python and verbose languages. Recently, the cryptography module made some significant changes in how the sign digital certificates. Some work was already done by another part time commuter from PyCon. But it worked only on higher versions of python but not backward compatible. My job was to write a solution that could both use the new method of signing certificates and also retain backward compatibility(at least for the moment). Now how the initial solution used to work was first by allocating a buffer memory and signing that certificate. But with the new PKCS7 method, that part of creating a memory allocation was handled. But python2.7 hasn't received any cryptography updates since cryptography 3.4.7 meanwhile the latest version as of this post is V41.0,1. After multiple iterations, I was able to come up with a solution to solve this and thanks to the help of one of the mentors, I passed all the build tests.

WHAT WILL I DO THIS WEEK?

This week, My target will be to have 3 PR's merged including the one I was working on this week. And also start documenting the Github actions workflow for building PyAfipWs Web Service Installers.

But Until then, See y'all next week

WEEKLY BLOG POST #3- GSOC Week 3

hanslettthedev@gmail.com (hanslett12) — Wed, 14 Jun 2023 12:33:55 +0000

It's week three, and things are not looking too good on my side. I have not yet been able to have even one PR merged. This is very worrying as it could affect my evaluation period. Here is a brief explanation of how my week 3 went

What did I do this week?

This week continues from where I left off, and that was working on upgrading the cryptography module of the web services of PyAfipWs. But unfortunately, One of the build processes kept failing on python2.7. This was particularly annoying as I was looking forward to finally merging my first PR!

A hurdle keeps appearing after every success

I was this close to merging the pull request. But one of the builds kept failing on python2.7. Worst case is I was reminded by my mentors again for the third week to write my blog post. Which is quite bad and I have to rectify. But back to the main discussion. They are 5 checks before a PR is merged to the main branch. I passed 4 and failed 1 which is to test the build on python2.7. Worst case is the test just fails unexpectedly without any proper error message even after adding debug flags when testing

What is coming next?

The GSOC evaluation period is fast approaching. And without a PR merged, I think I must complete at least 2 PR's this week. Secondly I need to start working on the next implementation for our Github actions auto release deploy. I hope the next time I'm writing an Article, It should be full of Good news!

Until next week, Have a great day

WEEKLY BLOG POST #2- GSOC Week 2

hanslettthedev@gmail.com (hanslett12) — Wed, 07 Jun 2023 10:57:31 +0000

It's me again lol! Another week has gone by and it's time to share my story again with y'all. Sorry I'm a bit late on schedule. This week was kind off a bad one for me but some good things did happen. Let me give you a recap!!!

What did I do this week?

This week, I had to continue working on an issue to fix existing unit tests that were broken due to a pull request. The code base I'm working with has backward compatibility with python 2.7 and it has some legacy modules to support some old devices. So this is not a simple tweak option where one can just remove a piece of code anyhow. Now I had to run the pytest module so it tests the whole application before I proceed making those changes

An unexpected issue occurred this week

I usually use windows to code and ubuntu when needed. I was running the tests on windows and they kept failing completely. So I decided to switch to ubuntu and voila, everything started working fine. Later on, I wanted to make a change to the above issue I was working with, and suddenly after making the changes and trying to run the tests, they kept failing. Now on ubuntu, I faced the same issue on windows. I spoke with my mentors and they did their best to help out. Eventually, I switched back to windows and with the help of one of the administrators, I was able to get everything working thanks to the help of one of my mentors. But clearly it seems the PR caused some weird bugs

What is coming next?

I'm currently trying to complete solving the issue one of the mentors gave me. Along side that, I have to start working and analyzing a Github actions script and to be able to provide a more improved action. I've never used github actions before, So I'm studying and reading from a book and applying it

I hope to see you reading again on monday, but until then, Ciao

WEEKLY BLOG POST #1 - GSOC Week 1

hanslettthedev@gmail.com (hanslett12) — Thu, 01 Jun 2023 07:20:48 +0000

Hello there, My name is Hanslett. This is my first blog post on the GSOC weekly timeline. It's my first post, so it won't be that fun but I promise it will get interesting overtime!

I have the honor to contribute to the PyAr|PyAfipWs organization

Let me share with you how my week went!

What did I do this week?

Well where do I start? Ok, I started out with working on an issue one of my org mentors suggested! This particular issue required me to run a bunch and try to patch a certain pull request to the unit test as some of the test cases where failing. I started running the tests, and for some reason, they kept failing. And thanks to the assistance of my mentors, I was able to get it up and running and start working on solving the broken tests.

What Is Coming up next?

I'll be working in the next few weeks on the github actions for automatically launching the build processes. My aim is to fully understand how github actions works and to be able to build the required installers for the next release of the project.

Did you get stuck anywhere?

Well, what is programming without any mistakes!!!!. I made a bunch of them and my mentors helped me out in resolving the issues. Just to summarize the issues, I had an issue with running the unit tests, Understanding some of the functionality since the code base is written in another language other than my native(English). But It's so much fun!!!

That's all for this week y'all. hopefully, you'll follow me through for next week because I'm sure, I'll have a very interesting story to tell you about github actions! Until then, have a great day fam!!!!1