Open blackmirag3 opened 4 months ago
Thank you for reporting the issue regarding the lack of exception handling for a corrupted split expenses file that results in the program crashing. While this is a significant issue that definitely requires attention to improve the robustness of the application, classifying it as high severity may not accurately reflect the typical user experience and the conditions under which this bug impacts the software. Therefore, I propose that it be classified as medium severity for the following reasons:
Uncommon Scenario: The occurrence of a corrupted split expenses file under normal usage conditions is relatively rare. Files typically become corrupted due to unusual events such as system crashes, hardware failures, or incorrect manual edits. Most users are unlikely to encounter this issue frequently, if at all, during the routine operation of the application.
User Control and Prevention: The file corruption leading to a crash, while serious when it occurs, is largely preventable through user education and more robust file handling practices such as validations- before edits and backups. These measures can mitigate the risk of corruption and reduce the likelihood of encountering this issue.
Impact on Core Functionality: Although the crash does affect those who experience it, the bug does not impact the fundamental usability of the software for all users. It is a specific error that affects the system only under certain conditions, as opposed to a pervasive or systemic flaw that would compromise the overall functionality or security of the application for every user.
Team chose [response.NotInScope
]
Reason for disagreement: I feel that this bug is something the team ought to have accounted for in this release and is hence within scope.
The UG pushes for manual editing of files including "SplitExpensesFile.txt" in chapter 6.2. This clearly is an intended feature that does not work correctly.
Course website: response.NotInScope: It is a valid issue but not something the team should be penalized for e.g., it was not related to features delivered in v2.1 or lower priority than the work already doen in v2.1.
When I edit the split expenses file wrongly, the programme seems to lack exception handling for this error and crashes.