Week 15 (July 29th - July 31st)
First of all, during this fifteenth week of intership, I have continued to investigate the upgrade to Node 17 and have finally managed to get it working. To do so, I have updated, via the yarn.lock file, the version of the lint-staged dependency to match the one used in Unibotics. Since Execa is a lint-staged dependency, updating the lint-staged version and installing the dependencies with yarn also updates the Execa version to the one used in Unibotics, thus supporting Node 17. So far, I have tried to run a couple of Robotics Academy exercises on my local deployment and everything seems to be working correctly.
However, when I went to push my solution to the final branch, I saw that the yarn.lock file seems to be updated by dependentbot[bot]. So, I asked about it to learn about the correct yarn.lock update process.
Also, when I tried to test the Node changes applied to the branch in Robotics Academy, the page went blank and a lot of problems popped up. It seems that these are not related to Node, but I am going to finish reviewing it and updating it properly after August holidays.
On the other hand, I have been helping to review the solution applied to issue 2665 of the labels of Robotics Academy exercises that I opened last week. In the first review carried out, errors were still detected. However, in the review of the final solution, I have observed that the Learn More button now works correctly in all the Robotics Academy exercises, both in user mode and in developer mode. In order for the solution to work in user mode, it has been necessary to generate a Robotics Backend test image 4.6.5-beta that includes the solution applied in the main branch, since the current RB, 4.6.4, did not include it, causing the error to occur when testing the labels on the first review. Therefore, the labels now work properly.
I have also been checking the functioning of the debug messages via the user console in Robotics Academy in user mode with the Robotics Backend 4.6.5-beta test image. As far as I have been able to observe, everything works correctly in all exercises for all types of errors: syntax, dependency or runtime errors. However, I have detected a problem in the case of syntax or dependency errors in the Rescue People exercise, by which these are not shown in the user console, although they are in the developer console and in the Robotics Backend. It seems that it is related to the launcher used by RAM in this type of exercises with drones. I have reported this and opened an issue.
Finally, I have continued researching the migration process from node-sass to sass. I have found out that the minimum supported version of Node for sass is 12. As for dependencies, there should be no problems with them. I will start the migration process after the holidays.
As for the broken pipe issue, I haven't been able to make any progress on it, but I have spoken to my co-worker David Duro about it, as he is also working on ports.
