search

adamzzq / pe

0 stars 0 forks source link

Unhandled exception #3

Open adamzzq opened 2 months ago

adamzzq commented 2 months ago

image.png

image.png The exceptions are thrown once there are large numbers in transaction values, I think it tries to erase the existing data once some invalid info is detected, but somehow it fails.

It stops showing exceptions if I manually delete that transactions.txt.

soc-se-bot commented 2 months ago

[IMPORTANT!: Please do not edit or reply to this comment using the GitHub UI. You can respond to it using CATcher during the next phase of the PE]

Team's Response

The root cause of this bug same as in issue #1407, as the group is deleted upon detecting corrupted data, leaving no groups left in groupList and resulting in the bug.

We agree with the reported bug. It was an implementation error that we did not account for upon restarting the application.

The 'Original' Bug

[The team marked this bug as a duplicate of the following bug]

Storage file corrupted

When I delete all groups and exit the bot, when reloading the bot I have an exception thrown and I cannot proceed to use the bot.

image.png

[original: nus-cs2113-AY2324S2/pe-interim#1270] [original labels: type.FunctionalityBug severity.High]

Their Response to the 'Original' Bug

[This is the team's response to the above 'original' bug]

We agree with the reported bug. After reviewing and testing, it was an implementation error that we did not account for upon restarting the application after integrating the function to exit the application after entering "close" or "exit" in the group creation phase.

Items for the Tester to Verify

:question: Issue duplicate status

Team chose to mark this issue as a duplicate of another issue (as explained in the Team's response above)

Reason for disagreement: [replace this with your reason]