Open xqtann opened 1 week ago
Team chose [response.Rejected
]
Reason for disagreement: Thank you for your response!
I would like to further explain my rationale of reporting the issue and marking it as severity.HIGH
.
From the screenshot you attached, there is a line that says that the mistakes "should not crash the app, corrupt the data, or make it unusable". I believe that this bug can be considered a very severe bug, since it could lead to actual data corruption and data loss, making the app fully unusable for a normal user.
Furthermore, the command I entered was just an example because I was not sure of what was the 'cut off' input cost for this bug to happen, and I had insufficient time in PE to investigate further. I hope you understand.
In actual fact, the data loss still occurs even with a much smaller and reasonable input cost (eg. $2000
) .
I have attached a video below to demonstrate the occurrence of the bug even with reasonably small input cost.
video:https://raw.githubusercontent.com/xqtann/pe/main/files/3bc8e131-9727-4f32-982e-a30413a54d30.mov
Whole app data was lost when I exited and re-entered the app upon doing the following steps:
inspect 1
to inspect Alex Yeohadd i/Chair e/2025-04-04 a/John street, block 123, #01-01, S123456 c/$200000000000000000000000 s/delivered
. (command is executed successfully without any error thrown)Expected: error to be thrown initially when app cannot handle such big number.