soc-pe-bot
commented
7 months ago Team's Response
Hi, thanks for bringing this up.
As seen from the extreme user behaviour in this section, where the issue is caused by integer overflow, which is caused by extreme user behaviour, it is not considered a bug. Additionally, this does not crash the app, corrupt the data, or make it unusable.
Hence, we are rejecting this bug, hope this clarifies!
This is a duplicater of #1853
The 'Original' Bug
[The team marked this bug as a duplicate of the following bug]
Incorrect error message for set-author
when entering an index out of bounds for set-author, the program should inform me to enter a valid index. However when entering too big a index it says the description is not a valid number, which is incorrect as the number is already entered before the description but not accounted for
[original: nus-cs2113-AY2324S2/pe-interim#1647] [original labels: type.FeatureFlaw severity.Medium]
Their Response to the 'Original' Bug
[This is the team's response to the above 'original' bug]
Hi thanks for pointing this out! However according to the course website,
Problems caused by extreme user behaviors: If the problems can only happen in case of deliberate sabotage (e.g., user entered a 30-digit telephone number), in which case it should not be considered a bug.
As such, since the input is a 100+ digit index this should not be considered a bug.
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)
- [ ] I disagree
Reason for disagreement: [replace this with your explanation]
## :question: Issue response Team chose [`response.Rejected`] - [ ] I disagree **Reason for disagreement:** [replace this with your explanation]
when removing a genre of invalid index number, the programme should output that the index is out of bounds, as so in removing index 6 and 60. However when the number gets too big the programme outputs invalid command.