Week 50. User code gets emptied at parsing
I located the problem: the code from the user was being deleted inside the exercise.py so, what I need to do now is finding the point where it gets emptied.
Posts by Tag
- GitHub 44
- Unibotics 33
- selenium 24
- Selenium 14
- ROS 10
- python 4
- week 31 2
- OpenCV 2
- week 0 1
- week 1 1
- week 2 1
- week 3 1
- week 4 1
- week 5 1
- week 6 1
- week 7 1
- week 8 1
- week 9 1
- week 10 1
- week 11 1
- week 12 1
- week 13 1
- week 14 1
- week 15 1
- week 16 1
- week 17 1
- week 18 1
- week 19 1
- week 20 1
- week 21 1
- week 22 1
- week 23 1
- week 24 1
- week 25 1
- week 26 1
- week 27 1
- week 28 1
- week 29 1
- week 30 1
- ImageProcessing 1
- week 33 1
- week 34 1
- week 35 1
- week 36 1
- week 37 1
- week 38 1
- week 39 1
- week 40 1
- week 41 1
- week 42 1
- week 43 1
- week 44 1
- week 45 1
- week 46 1
- week 47 1
- week 48 1
- week 49 1
- week 50 1
GitHub
Week 49. Code sent by the user is empty
So, with the discovery of the previos week, I now can debug with more ease.
Week 48. Addind time.sleep to avoid errors & checking the exercise again
Even after using the invisibility_of_element_located function, or the selenium methods to wait for an element to be clickable, some errors still happened.
Week 47. Submit button obscured by a modal
I found the reason for getting that timeout errors the previous week.
Week 46. Changing the selection to react & test getting timeout
The main menu, where the exercises are collected, changed to react a while ago. So now that I have a basic functionality test working, it’s time to change th...
Week 45. Differences between subprocess.Popen & subprocess.run
As I commented the previous week, one thing I need to keep in mind for these integration is that the RADI container must be up before trying to execute the n...
Week 44. Implementing individual functionality test
After the issue with ACE editor was solved in the previos week, my main task this week was to start implementing the test exercise by exercise.
Week 43. Insert code in ACE editor resolved
Finally this week the problem of inserting code in the ACE editor is resolved!
Week 42. Trying to debug image processing exercise
While the error when inserting code in ACE editor seems close to be resolved, this week I returned to the exercise implementation.
Week 41. Making the script for each topic
As studied in the previous weeks, a lot of exercises share topic so now I reproduced the shell script of the previous weeks with the rest of topics.
Week 40. Simplyfying and reusing scripts
With the fidings of the previous weeks, maybe two or three scripts per exercise were not really needed.
Week 39. Investigating how to handle topics
The objective of these test is checking wether, executing the user code, the robot changes it position or not.
Week 38. Trying to simplify the testing flow
The past week I was traveling, so I wasn’t able to write something for the blog.
Week 37. Modules problem & returning to automatic testing for a while
So, it looks like there is some problem with the PYTHONPATH in my new exercise, and because of that the modules cannot be “seen” when the code from user is e...
Week 36. Implementing image processing exercise pt.2
Afther checking everything was ok with raising the exercise, it was time to test it.
Week 35. Implementing image processing exercise
Once the manager.py and the flow is understood, it was time to really start implementing the exercise.
Week 33/34. Understanding manager.py pt.2
This two weeks were dedicated to completely understanding the manager.py.
Week 32. Understanding manager.py pt.1
As I was implementing the exercise I made a lot of errors.
Week 31. Start of a image processing exercise
This week, we are going to start with the implementation of a image processing exercise.
Week 30. Pausing functionality tests for now
I kept looking through the week to see if there is any other way of inserting text using Selenium or external functions. But there isn’t a lot of information...
Week 29. Trying to insert code in ACE editor pt.3
As I already knew the edits is a WebElement, I looked for ways of interacting with it using Selenium and asked my co-tutor about it. It seems that there is a...
Week 28. Trying to insert code in ACE editor pt.2
The send_keys function didn’t work, so now I have to look for another way of doing it.
Week 27. Trying to insert code in ACE editor pt.1
Once I have the topic part, the next step is interacting with the ACE editor that the platform uses.
Week 26. Subprocess invoking .sh indifinitely waiting
As I added the subprocess line to the Selenium script I noticed that it got stuck and never gived an answer unless I stopped it manually.
Week 25. Invoking testing.py through a .sh script
I already made the .sh script.
Week 24. Adding a .sh script to be able to execute topics_testing.py
As i was trying to test the .sh script made the previous week… i got another error.
Week 23. More problems while trying to use topics_testing.py from outside container
The new approach was trying to make a script at the first level of the container.
Week 22. Trying to get the position from outside docker container
Once I had the script already working inside the container it was time to test it outside of it, in the same script as the test were being made.
Week 21. Trying to subscribe to one topic pt.4
Once the error of the previos week got resolved, i could keep trying to make my script work.
Week 19/20. Trying to subscribe to one topic pt.3
The problem with rospy continues, i can’t seem to find from where it comes so I need to ask for help to the rest of developers of unibotics.
Week 18. Trying to subscribe to one topic pt.2
First approach. Trying to make a python script that returns the position of the robot to me.
Week 17. Trying to subscribe to one topic
I already had a little notion of what a ros topic is, so now it’s time to start coding and finishing to understand how they really work.
Week 16. Checking ROS topics
I already could raise the RADI container and I knew how to use Selenium to raise a test server. So a few steps of the integration were already done.
Week 15. Understanding subprocess module
First thing I need to do in my functionality test: Make the RADI container available. In order to do that, normally, i would type docker start RADI in my lin...
Week 14. Functionality test draft
Once the frontend tests are finished and working, the next step is to start with the functionality tests for the production exercises.
Week 13. Explaining the test, note to my future self
Although the test code may seem simple or repetitive at first glance, there is a lot behind it. That’s why I think it’s good to make this blog post, even if ...
Week 12. Uploading frontend automatic testing
Once the test are made, it was time to make one file that contained them all.
Week 11. Finalizing frontend automatic tests
This week I ended developing and evolving the frontend test por the unibotics-webserver repository.
Week 10. Uploading Selenium Test for Unibotics
I added automatic tests using Selenium for the frontend of unibotics. One test for each button separately.
Week 8/9. Uploading Selenium Test for Unibotics
The test for color_filter exercise are done. They are yet basic tests that check if the buttons on the page are clickable or not. There are many improvements...
Week 6/7. Creating Selenium Test
This weeks the work has been centered around implementing automatic test to the unibotic platform. That way, when a deployment is done, we could automaticall...
Week 5. First issue
As I continue to study the code of some files in the unibotics repository I helped solve a little issue!
Week 3. Unibotics introduction
The task for this week was getting familiar with the front-end of the unibotics repository.
Week 2. GitHub & Selenium
This week I had two main task:
Unibotics
Week 50. User code gets emptied at parsing
I located the problem: the code from the user was being deleted inside the exercise.py so, what I need to do now is finding the point where it gets emptied.
Week 49. Code sent by the user is empty
So, with the discovery of the previos week, I now can debug with more ease.
Week 37. Modules problem & returning to automatic testing for a while
So, it looks like there is some problem with the PYTHONPATH in my new exercise, and because of that the modules cannot be “seen” when the code from user is e...
Week 36. Implementing image processing exercise pt.2
Afther checking everything was ok with raising the exercise, it was time to test it.
Week 35. Implementing image processing exercise
Once the manager.py and the flow is understood, it was time to really start implementing the exercise.
Week 33/34. Understanding manager.py pt.2
This two weeks were dedicated to completely understanding the manager.py.
Week 32. Understanding manager.py pt.1
As I was implementing the exercise I made a lot of errors.
Week 31. Start of a image processing exercise
This week, we are going to start with the implementation of a image processing exercise.
Week 30. Pausing functionality tests for now
I kept looking through the week to see if there is any other way of inserting text using Selenium or external functions. But there isn’t a lot of information...
Week 29. Trying to insert code in ACE editor pt.3
As I already knew the edits is a WebElement, I looked for ways of interacting with it using Selenium and asked my co-tutor about it. It seems that there is a...
Week 28. Trying to insert code in ACE editor pt.2
The send_keys function didn’t work, so now I have to look for another way of doing it.
Week 27. Trying to insert code in ACE editor pt.1
Once I have the topic part, the next step is interacting with the ACE editor that the platform uses.
Week 26. Subprocess invoking .sh indifinitely waiting
As I added the subprocess line to the Selenium script I noticed that it got stuck and never gived an answer unless I stopped it manually.
Week 25. Invoking testing.py through a .sh script
I already made the .sh script.
Week 24. Adding a .sh script to be able to execute topics_testing.py
As i was trying to test the .sh script made the previous week… i got another error.
Week 23. More problems while trying to use topics_testing.py from outside container
The new approach was trying to make a script at the first level of the container.
Week 22. Trying to get the position from outside docker container
Once I had the script already working inside the container it was time to test it outside of it, in the same script as the test were being made.
Week 21. Trying to subscribe to one topic pt.4
Once the error of the previos week got resolved, i could keep trying to make my script work.
Week 19/20. Trying to subscribe to one topic pt.3
The problem with rospy continues, i can’t seem to find from where it comes so I need to ask for help to the rest of developers of unibotics.
Week 18. Trying to subscribe to one topic pt.2
First approach. Trying to make a python script that returns the position of the robot to me.
Week 17. Trying to subscribe to one topic
I already had a little notion of what a ros topic is, so now it’s time to start coding and finishing to understand how they really work.
Week 16. Checking ROS topics
I already could raise the RADI container and I knew how to use Selenium to raise a test server. So a few steps of the integration were already done.
Week 15. Understanding subprocess module
First thing I need to do in my functionality test: Make the RADI container available. In order to do that, normally, i would type docker start RADI in my lin...
Week 14. Functionality test draft
Once the frontend tests are finished and working, the next step is to start with the functionality tests for the production exercises.
Week 13. Explaining the test, note to my future self
Although the test code may seem simple or repetitive at first glance, there is a lot behind it. That’s why I think it’s good to make this blog post, even if ...
Week 12. Uploading frontend automatic testing
Once the test are made, it was time to make one file that contained them all.
Week 11. Finalizing frontend automatic tests
This week I ended developing and evolving the frontend test por the unibotics-webserver repository.
Week 10. Uploading Selenium Test for Unibotics
I added automatic tests using Selenium for the frontend of unibotics. One test for each button separately.
Week 8/9. Uploading Selenium Test for Unibotics
The test for color_filter exercise are done. They are yet basic tests that check if the buttons on the page are clickable or not. There are many improvements...
Week 6/7. Creating Selenium Test
This weeks the work has been centered around implementing automatic test to the unibotic platform. That way, when a deployment is done, we could automaticall...
Week 5. First issue
As I continue to study the code of some files in the unibotics repository I helped solve a little issue!
Week 4. D1 Deployment
Finally, I was able to solve the previous problems I faced while trying to make a D1 Deployment.
Week 3. Unibotics introduction
The task for this week was getting familiar with the front-end of the unibotics repository.
selenium
Week 32. Understanding manager.py pt.1
As I was implementing the exercise I made a lot of errors.
Week 31. Start of a image processing exercise
This week, we are going to start with the implementation of a image processing exercise.
Week 30. Pausing functionality tests for now
I kept looking through the week to see if there is any other way of inserting text using Selenium or external functions. But there isn’t a lot of information...
Week 29. Trying to insert code in ACE editor pt.3
As I already knew the edits is a WebElement, I looked for ways of interacting with it using Selenium and asked my co-tutor about it. It seems that there is a...
Week 28. Trying to insert code in ACE editor pt.2
The send_keys function didn’t work, so now I have to look for another way of doing it.
Week 27. Trying to insert code in ACE editor pt.1
Once I have the topic part, the next step is interacting with the ACE editor that the platform uses.
Week 26. Subprocess invoking .sh indifinitely waiting
As I added the subprocess line to the Selenium script I noticed that it got stuck and never gived an answer unless I stopped it manually.
Week 25. Invoking testing.py through a .sh script
I already made the .sh script.
Week 24. Adding a .sh script to be able to execute topics_testing.py
As i was trying to test the .sh script made the previous week… i got another error.
Week 23. More problems while trying to use topics_testing.py from outside container
The new approach was trying to make a script at the first level of the container.
Week 22. Trying to get the position from outside docker container
Once I had the script already working inside the container it was time to test it outside of it, in the same script as the test were being made.
Week 21. Trying to subscribe to one topic pt.4
Once the error of the previos week got resolved, i could keep trying to make my script work.
Week 19/20. Trying to subscribe to one topic pt.3
The problem with rospy continues, i can’t seem to find from where it comes so I need to ask for help to the rest of developers of unibotics.
Week 18. Trying to subscribe to one topic pt.2
First approach. Trying to make a python script that returns the position of the robot to me.
Week 17. Trying to subscribe to one topic
I already had a little notion of what a ros topic is, so now it’s time to start coding and finishing to understand how they really work.
Week 16. Checking ROS topics
I already could raise the RADI container and I knew how to use Selenium to raise a test server. So a few steps of the integration were already done.
Week 15. Understanding subprocess module
First thing I need to do in my functionality test: Make the RADI container available. In order to do that, normally, i would type docker start RADI in my lin...
Week 14. Functionality test draft
Once the frontend tests are finished and working, the next step is to start with the functionality tests for the production exercises.
Week 13. Explaining the test, note to my future self
Although the test code may seem simple or repetitive at first glance, there is a lot behind it. That’s why I think it’s good to make this blog post, even if ...
Week 12. Uploading frontend automatic testing
Once the test are made, it was time to make one file that contained them all.
Week 11. Finalizing frontend automatic tests
This week I ended developing and evolving the frontend test por the unibotics-webserver repository.
Week 10. Uploading Selenium Test for Unibotics
I added automatic tests using Selenium for the frontend of unibotics. One test for each button separately.
Week 8/9. Uploading Selenium Test for Unibotics
The test for color_filter exercise are done. They are yet basic tests that check if the buttons on the page are clickable or not. There are many improvements...
Week 6/7. Creating Selenium Test
This weeks the work has been centered around implementing automatic test to the unibotic platform. That way, when a deployment is done, we could automaticall...
Selenium
Week 50. User code gets emptied at parsing
I located the problem: the code from the user was being deleted inside the exercise.py so, what I need to do now is finding the point where it gets emptied.
Week 48. Addind time.sleep to avoid errors & checking the exercise again
Even after using the invisibility_of_element_located function, or the selenium methods to wait for an element to be clickable, some errors still happened.
Week 47. Submit button obscured by a modal
I found the reason for getting that timeout errors the previous week.
Week 46. Changing the selection to react & test getting timeout
The main menu, where the exercises are collected, changed to react a while ago. So now that I have a basic functionality test working, it’s time to change th...
Week 45. Differences between subprocess.Popen & subprocess.run
As I commented the previous week, one thing I need to keep in mind for these integration is that the RADI container must be up before trying to execute the n...
Week 44. Implementing individual functionality test
After the issue with ACE editor was solved in the previos week, my main task this week was to start implementing the test exercise by exercise.
Week 43. Insert code in ACE editor resolved
Finally this week the problem of inserting code in the ACE editor is resolved!
Week 42. Trying to debug image processing exercise
While the error when inserting code in ACE editor seems close to be resolved, this week I returned to the exercise implementation.
Week 41. Making the script for each topic
As studied in the previous weeks, a lot of exercises share topic so now I reproduced the shell script of the previous weeks with the rest of topics.
Week 40. Simplyfying and reusing scripts
With the fidings of the previous weeks, maybe two or three scripts per exercise were not really needed.
Week 39. Investigating how to handle topics
The objective of these test is checking wether, executing the user code, the robot changes it position or not.
Week 38. Trying to simplify the testing flow
The past week I was traveling, so I wasn’t able to write something for the blog.
Week 37. Modules problem & returning to automatic testing for a while
So, it looks like there is some problem with the PYTHONPATH in my new exercise, and because of that the modules cannot be “seen” when the code from user is e...
Week 2. GitHub & Selenium
This week I had two main task:
ROS
Week 48. Addind time.sleep to avoid errors & checking the exercise again
Even after using the invisibility_of_element_located function, or the selenium methods to wait for an element to be clickable, some errors still happened.
Week 47. Submit button obscured by a modal
I found the reason for getting that timeout errors the previous week.
Week 46. Changing the selection to react & test getting timeout
The main menu, where the exercises are collected, changed to react a while ago. So now that I have a basic functionality test working, it’s time to change th...
Week 45. Differences between subprocess.Popen & subprocess.run
As I commented the previous week, one thing I need to keep in mind for these integration is that the RADI container must be up before trying to execute the n...
Week 44. Implementing individual functionality test
After the issue with ACE editor was solved in the previos week, my main task this week was to start implementing the test exercise by exercise.
Week 43. Insert code in ACE editor resolved
Finally this week the problem of inserting code in the ACE editor is resolved!
Week 42. Trying to debug image processing exercise
While the error when inserting code in ACE editor seems close to be resolved, this week I returned to the exercise implementation.
Week 41. Making the script for each topic
As studied in the previous weeks, a lot of exercises share topic so now I reproduced the shell script of the previous weeks with the rest of topics.
Week 40. Simplyfying and reusing scripts
With the fidings of the previous weeks, maybe two or three scripts per exercise were not really needed.
Week 39. Investigating how to handle topics
The objective of these test is checking wether, executing the user code, the robot changes it position or not.
python
Week 5. First issue
As I continue to study the code of some files in the unibotics repository I helped solve a little issue!
Week 4. D1 Deployment
Finally, I was able to solve the previous problems I faced while trying to make a D1 Deployment.
Week 2. GitHub & Selenium
This week I had two main task:
Week 1. Python & GitHub review
This first week the task was simple: review the Python syntax so I can use this language on the rest of the TFG.
week 31
Week 32. Understanding manager.py pt.1
As I was implementing the exercise I made a lot of errors.
Week 31. Start of a image processing exercise
This week, we are going to start with the implementation of a image processing exercise.
OpenCV
Week 50. User code gets emptied at parsing
I located the problem: the code from the user was being deleted inside the exercise.py so, what I need to do now is finding the point where it gets emptied.
Week 49. Code sent by the user is empty
So, with the discovery of the previos week, I now can debug with more ease.
week 0
Introduction
First post
week 1
Week 1. Python & GitHub review
This first week the task was simple: review the Python syntax so I can use this language on the rest of the TFG.
week 2
Week 2. GitHub & Selenium
This week I had two main task:
week 3
Week 3. Unibotics introduction
The task for this week was getting familiar with the front-end of the unibotics repository.
week 4
Week 4. D1 Deployment
Finally, I was able to solve the previous problems I faced while trying to make a D1 Deployment.
week 5
Week 5. First issue
As I continue to study the code of some files in the unibotics repository I helped solve a little issue!
week 6
Week 6/7. Creating Selenium Test
This weeks the work has been centered around implementing automatic test to the unibotic platform. That way, when a deployment is done, we could automaticall...
week 7
Week 6/7. Creating Selenium Test
This weeks the work has been centered around implementing automatic test to the unibotic platform. That way, when a deployment is done, we could automaticall...
week 8
Week 8/9. Uploading Selenium Test for Unibotics
The test for color_filter exercise are done. They are yet basic tests that check if the buttons on the page are clickable or not. There are many improvements...
week 9
Week 8/9. Uploading Selenium Test for Unibotics
The test for color_filter exercise are done. They are yet basic tests that check if the buttons on the page are clickable or not. There are many improvements...
week 10
Week 10. Uploading Selenium Test for Unibotics
I added automatic tests using Selenium for the frontend of unibotics. One test for each button separately.
week 11
Week 11. Finalizing frontend automatic tests
This week I ended developing and evolving the frontend test por the unibotics-webserver repository.
week 12
Week 12. Uploading frontend automatic testing
Once the test are made, it was time to make one file that contained them all.
week 13
Week 13. Explaining the test, note to my future self
Although the test code may seem simple or repetitive at first glance, there is a lot behind it. That’s why I think it’s good to make this blog post, even if ...
week 14
Week 14. Functionality test draft
Once the frontend tests are finished and working, the next step is to start with the functionality tests for the production exercises.
week 15
Week 15. Understanding subprocess module
First thing I need to do in my functionality test: Make the RADI container available. In order to do that, normally, i would type docker start RADI in my lin...
week 16
Week 16. Checking ROS topics
I already could raise the RADI container and I knew how to use Selenium to raise a test server. So a few steps of the integration were already done.
week 17
Week 17. Trying to subscribe to one topic
I already had a little notion of what a ros topic is, so now it’s time to start coding and finishing to understand how they really work.
week 18
Week 18. Trying to subscribe to one topic pt.2
First approach. Trying to make a python script that returns the position of the robot to me.
week 19
Week 19/20. Trying to subscribe to one topic pt.3
The problem with rospy continues, i can’t seem to find from where it comes so I need to ask for help to the rest of developers of unibotics.
week 20
Week 19/20. Trying to subscribe to one topic pt.3
The problem with rospy continues, i can’t seem to find from where it comes so I need to ask for help to the rest of developers of unibotics.
week 21
Week 21. Trying to subscribe to one topic pt.4
Once the error of the previos week got resolved, i could keep trying to make my script work.
week 22
Week 22. Trying to get the position from outside docker container
Once I had the script already working inside the container it was time to test it outside of it, in the same script as the test were being made.
week 23
Week 23. More problems while trying to use topics_testing.py from outside container
The new approach was trying to make a script at the first level of the container.
week 24
Week 24. Adding a .sh script to be able to execute topics_testing.py
As i was trying to test the .sh script made the previous week… i got another error.
week 25
Week 25. Invoking testing.py through a .sh script
I already made the .sh script.
week 26
Week 26. Subprocess invoking .sh indifinitely waiting
As I added the subprocess line to the Selenium script I noticed that it got stuck and never gived an answer unless I stopped it manually.
week 27
Week 27. Trying to insert code in ACE editor pt.1
Once I have the topic part, the next step is interacting with the ACE editor that the platform uses.
week 28
Week 28. Trying to insert code in ACE editor pt.2
The send_keys function didn’t work, so now I have to look for another way of doing it.
week 29
Week 29. Trying to insert code in ACE editor pt.3
As I already knew the edits is a WebElement, I looked for ways of interacting with it using Selenium and asked my co-tutor about it. It seems that there is a...
week 30
Week 30. Pausing functionality tests for now
I kept looking through the week to see if there is any other way of inserting text using Selenium or external functions. But there isn’t a lot of information...
ImageProcessing
Week 31. Start of a image processing exercise
This week, we are going to start with the implementation of a image processing exercise.
week 33
Week 33/34. Understanding manager.py pt.2
This two weeks were dedicated to completely understanding the manager.py.
week 34
Week 33/34. Understanding manager.py pt.2
This two weeks were dedicated to completely understanding the manager.py.
week 35
Week 35. Implementing image processing exercise
Once the manager.py and the flow is understood, it was time to really start implementing the exercise.
week 36
Week 36. Implementing image processing exercise pt.2
Afther checking everything was ok with raising the exercise, it was time to test it.
week 37
Week 37. Modules problem & returning to automatic testing for a while
So, it looks like there is some problem with the PYTHONPATH in my new exercise, and because of that the modules cannot be “seen” when the code from user is e...
week 38
Week 38. Trying to simplify the testing flow
The past week I was traveling, so I wasn’t able to write something for the blog.
week 39
Week 39. Investigating how to handle topics
The objective of these test is checking wether, executing the user code, the robot changes it position or not.
week 40
Week 40. Simplyfying and reusing scripts
With the fidings of the previous weeks, maybe two or three scripts per exercise were not really needed.
week 41
Week 41. Making the script for each topic
As studied in the previous weeks, a lot of exercises share topic so now I reproduced the shell script of the previous weeks with the rest of topics.
week 42
Week 42. Trying to debug image processing exercise
While the error when inserting code in ACE editor seems close to be resolved, this week I returned to the exercise implementation.
week 43
Week 43. Insert code in ACE editor resolved
Finally this week the problem of inserting code in the ACE editor is resolved!
week 44
Week 44. Implementing individual functionality test
After the issue with ACE editor was solved in the previos week, my main task this week was to start implementing the test exercise by exercise.
week 45
Week 45. Differences between subprocess.Popen & subprocess.run
As I commented the previous week, one thing I need to keep in mind for these integration is that the RADI container must be up before trying to execute the n...
week 46
Week 46. Changing the selection to react & test getting timeout
The main menu, where the exercises are collected, changed to react a while ago. So now that I have a basic functionality test working, it’s time to change th...
week 47
Week 47. Submit button obscured by a modal
I found the reason for getting that timeout errors the previous week.
week 48
Week 48. Addind time.sleep to avoid errors & checking the exercise again
Even after using the invisibility_of_element_located function, or the selenium methods to wait for an element to be clickable, some errors still happened.
week 49
Week 49. Code sent by the user is empty
So, with the discovery of the previos week, I now can debug with more ease.
week 50
Week 50. User code gets emptied at parsing
I located the problem: the code from the user was being deleted inside the exercise.py so, what I need to do now is finding the point where it gets emptied.