Oliver’s Status Report – 16 Apr 22

This week I have been working on testing and ironing the bugs that have been identified. One bug that cropped up during the demo presentation itself was a bug in the backend logic that was resulting in items not being properly decremented after removal. This stemmed from our transaction-oriented database design, where instead of a running total, a list of transaction deltas are stored in the database instead. A bug in the logic in collapsing these transactions (i.e. one loop was reading from the front while an inner loop was reading from the back) resulted in the unexpected behavior. Fixing this bug was relatively nasty as it meant having to store more information for computation – the original quantities of each addition. This bit of logic was especially complicated, due to the simultaneous “first-in-first-out with replacement” nature of our application.

Additionally, I have also began work to expand the database to support presenting nutritional information, a new feature we are planning to introduce. I will be expanding the schema by adding new tables, and creating new API endpoints for the new feature. I expect this will take around 1-2 weeks.

Overall, we are on track and I am personally confident in our ability to finish this project satisfactorily.

Leave a Reply

Your email address will not be published. Required fields are marked *