In this blog, I'll be posting about my experience as an intern at JdeRobot.
First, during this eighth week of internship, I have been reviewing the Global Navigation exercise of Unibotics 3.10, locally and remotely, given the problems indicated by some students in the university’s Virtual Classroom. After several tests, I checked that everything worked correctly and that the errors indicated did not appear.
However, during this test, I detected an error during the registration process of new users in Unibotics, when trying to create an account, by which the account is not created correctly due to the activation email not being send correctly. I have opened an issue about this problem and I will try to solve it in the coming days.
Also, I have noticed that the MainAppBar of the Unibotics 3.10 Autoparking exercise, both remotely and locally, becomes bigger and disorganizes in worlds with very long names. I have opened an issue of this problem.
Continuing with the tests of the exercises, after checking the Global Navigation exercise, I have been reviewing and checking the other ROS2 exercises of Unibotics 3.10, both locally and remotely, to check that everything works properly after the renewal of certificates and the resolution of problems, indicated by the students, done by my co-wokers. Through these tests, I have verified that everything works correctly.
On the other hand, during the week, I created an account to access the D2 deployment machines and, once I was given access, I tested these machines to check that I could access them correctly.
Subsequently, I switched to the issue 1232 branch to help my co-worker Carlos make the exercises use Robotics Academy's widgets and Unibotics-specific's widgets. Also, I have been researching the code of the templates of the exercises to see how they are using the components, as well as having a meeting with Carlos about the widgets.
As indicated by Carlos, one of the problems is that, when executing a Robotics Academy exercise, its components are not well detected. After researching this, reviewing the react_components and exercise-index scripts, among others, we have discovered that the problem comes from how webpack generates component's dependencies based on entry points and how it builds the dependency graph. After researching more about it and the different types of entry points in webpack, I discovered that we could use a multi-main entry in the exercise entry point of Unibotics to pass an array of files indicating the exercise-index of Unibotics and RA and thus creating a graph with the combined dependencies, thus solving the problem we had.
However, there is a new problem by which, when launching a Unibotics exercise, it does not detect the modules of its components, such as ExerciseControl, as it goes to search for them in the Robotics Academy files. This problem is what we will be working on in the coming days.
On the other hand, I have been reviewing the registry error in Unibotics and researching the urls.py and views.py scripts of commons and Academy in order to discover which URL is not being detected (activate).
Finally, I have been reviewing the kart problem when you change world in the Follow Line exercise to open the incidence this next week.