search

imanamirshah / pe

0 stars 0 forks source link

Unable to recognise two task with same index when deleting #12

Open imanamirshah opened 7 months ago

imanamirshah commented 7 months ago

image.png

image.png

There are 2 items with the same index here after I corrupted the file. Program does not identify this and proceeds to delete the first instance of index 1.

soc-se-bot commented 7 months ago

Team's Response

If you add tasks using the terminal, the task number will always be different(incremented) when new tasks are added. The issue you raised is because you edited the txt file that write into your local, which is not a expected action at all.

The 'Original' Bug

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

No checks for corrupted file, exception is not caught

image.png

image.png

I corrupted the data file as seen above by removing the f from type and a + from the table. It results in a thrown exception as seen above. File corruption is not handled upon starting of the app.

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

Their Response to the 'Original' Bug

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

Dealing with corrupted files is not in the scope of our user task, thus implementing this feature was not part of the task to accomplish. Purposely corrupting the file of course will create a bug if corrupted file detection is not implemented.

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 explanation]

## :question: Issue response Team chose [`response.NotInScope`] - [ ] I disagree **Reason for disagreement:** [replace this with your explanation]
## :question: Issue severity Team chose [`severity.High`] Originally [`severity.Medium`] - [ ] I disagree **Reason for disagreement:** [replace this with your explanation]