Open MonkeScripts opened 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]
Duplicate of #854.
Huh? What are you trying to show here?
Also, is there any proof of overflow? Your extremely large input was correctly caught by the application and treated as invalid. How can there be overflow when your input has been invalidated in the first place?
This is also obviously an example of extreme user behaviour.
[The team marked this bug as a duplicate of the following bug]
Integer overflow for all whole number outputs
[original: nus-cs2113-AY2324S2/pe-interim#777] [original labels: type.FunctionalityBug severity.High]
[This is the team's response to the above 'original' bug]
Clearly an example of extreme user behavior. Noted on the attempts to try some sort of input injection attacks as well 🙄.
Anyway, there is obviously no integer overflow in this case. The extremely large threshold value, which you tried to input, was correctly caught by the application and treated as invalid.
How can you therefore say that there is an overflow when your input has been invalidated and not accepted by the application?
High bug severity is completely unjustified and unwarranted as well, since there is no concrete proof of "integer overflow" in your attached screenshot. I'll reduce its severity to Low.
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]