This week, as a mentor, I did the classly announcements and attendance on Tuesday, but was sick on Friday so I couldn’t come, but I made to sure let the other mentors in my room know as soon as I could so they could cover for me. I also did my workshop on Wednesday, which was an introduction to the database query language PostgreSQL. It went well, and a dozen or so people came to learn about psql, where I made sure to do a demonstration where people could follow along in their own psql terminal, answer questions, and supply a postgres cheat sheet for things like viewing or connecting to databases/tables, creating and editing tables, etc. As a student, I looked into how to approach the redis cache dump issue and talked to our project lead Joel, who had a good idea on how to solve it. I’m now going through the codebase to learn about redis and how shubble uses it, but that’s just what I’ve done with shubble. For EzASM, I think I finally got to the bottom of the problem about the malloc and free pull feature addition. I made some commits adding tests to get a better understanding of them, and now that I know how to fix it, I removed most of what I added, but also fixed the issue that was bugging me.

Next week, as a mentor, I plan on following up with some students regarding their mid-semester summaries. Some students seemed to be in a tough situation regarding their ability to make a lot of commits, usually because they weren’t in positions of coding, but physical electrical engineering or 3d modeling. I didn’t get the chance to this week because I was sick Friday, but hopefully I can help them get on track to do well for the final commit summary. As a student, I plan on reviewing and merging the pull request I finished, since I’m not sure Collin will be in a position to review it. I suppose I’ll ask him if he could review mine if I promise to review his pull requests in return. Additionally, I’ll get some work done on the shubble redis issue by doing work on the worker loop, more specifically dumping the cache whenever it’s reinitialized, but being careful not to put it in the loop itself, since that could be costly.