You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The same kind of invalid input(route of index not exists), but getting different exception message. The second exception message should be undefined behavior.
Moreover, there is actually a bound of number of routes in the app, which is 2147483647, because the previous inconsistent exception message reflects that the data type used to storing the number of routes is an "int", which has naturally bound 2147483647. Without declaration, the records will be overwritten when the number of routes exceeds 2147483647.
This problem of integer overflow can only happen in case of deliberate sabotage. The app does not crash and the input is not accepted. Thus the data will not be corrupted. Therefore, we think that it is more reasonable to be a low severity bug.
This is consistent with the specification on module website:
The same kind of invalid input(route of index not exists), but getting different exception message. The second exception message should be undefined behavior.
Moreover, there is actually a bound of number of routes in the app, which is 2147483647, because the previous inconsistent exception message reflects that the data type used to storing the number of routes is an "int", which has naturally bound 2147483647. Without declaration, the records will be overwritten when the number of routes exceeds 2147483647.
[original: nus-cs2113-AY2122S2/pe-interim#1311] [original labels: severity.Medium type.FunctionalityBug]
The text was updated successfully, but these errors were encountered: