Welcome to my internship work blog!

In this blog, I'll be posting about my experience as an intern at JdeRobot.

Week 5 (May 20th - May 24th)

First of all, during this fifth week of internship, I have finished reviewing and correcting the errors marked in the Unibotics D1 deployment documentation issue, making a pull request to merge it with the main branch.

On the other hand, I have continued researching on how to pull branches with submodules to be able to bring the branch of the issue locally in order to work on it. Finally, I have achieved it and now I have the issue branch locally on my computer.

Additionally, I have been researching about submodules and webpack, through different articles and videos, to get a general idea and start helping with issue 1219. I have also checked the Unibotics webpack configuration file in order to have a better understanding of what I have learned about webpack.

Continuing with the investigation of issue 1219, I have been researching the webpack-related errors that appeared when I tried to connect to the exercises. Specifically, I focused on the Rescue People exercise. In this case, the error was related to missing modules. In essence, the html template of the exercise was looking for certain modules (files) among the Robotics Academy files, but using the Unibotics path.



Module not found error - Unibotics issue 1219


Despite this, when I had determined a possible solution, I realized, thanks to the help of my co-worker Carlos, that the errors that appeared in my case were not the same errors that he presented, which were related to hooks.

While researching this difference between the errors, I discovered that certain files had not been cloned and pulled correctly and were not based on the last commit performed. Because of this, I have repeated the clone and pull process of the issue branch using GitHub Desktop. However, although now the files have been cloned correctly, the same module not found error keeps showing up. I’m going to keep investigating about it to discover why this might be happening.

Lastly, I have been reviewing with Carlos the React hook error, evaluating different possibilities such as, for example, an error related to the webpack loaders. Finally, Carlos has discovered that the error comes from the webpack nodes used in Unibotics. Now, by temporarily using Robotics Academy nodes, we have a prototype exercise. In this case, a new error has appeared, related to a configuration variable, in which I will focus these days to try to solve it.

JdeRobot logo URJC and ETSII logo