nus-pe-bot
commented
4 years ago Team's Response
Not a bug. The log is not meant for end-users to read. It's meant for developers, when debugging.
Like, really, go look at any other GUI app, especially Linux GUI apps. They throw tons of exceptions to stderr. It's normal.
Anyway, AB3 also throws a warning on stderr on first startup. I just print the stack trace along with it. Again, the log of a GUI app is meant for debugging.
Here, look at the stderr output of Firefox. Many errors, none of them consequential.
Or the browser console. Even more errors.
But as an end-user that's not meant for you to care about.
Items for the Tester to Verify
:question: Issue response
Team chose [response.Rejected]
- [ ] I disagree
Reason for disagreement: [replace this with your reason]
:question: Issue severity
Team chose [severity.Low].
Originally [severity.Medium].
- [ ] I disagree
Reason for disagreement: [replace this with your reason]
:question: Issue type
Team chose [type.FunctionalityBug].
Originally [type.FeatureFlaw].
- [ ] I disagree
Reason for disagreement: [replace this with your reason]
Upon running the jar file for the first time, there is a storage related exception being thrown on terminal. This should be handled more gracefully, perhaps by telling the user (on the UI) that there is no data to load and that the app will be starting with a sample or empty file instead. This would be better than an exception being shown on the terminal.