search

nkotaa / pe

0 stars 0 forks source link

Unable to display recommended schedules #3

Open nkotaa opened 2 months ago

nkotaa commented 2 months ago

Steps to reproduce

  1. Start up program as directed in an empty directory
  2. Run display BME

Expected

Displays the recommended BME curriculum schedule.

Actual

2024-04-19T16:34:40,333543359+08:00.png

Bug has been reproduced with other major names as well.

nus-pe-bot commented 2 months ago

Team's Response

This issue is actually caused by the missing disclaimer for Linux users in the UG ("original" issue #2511). In the UG, we have specified that MacOS users must download the data.zip file, as otherwise, the same error message as shown by the tester will be seen. However, we have missed out the disclaimer for Linux users.

The 'Original' Bug

[The team marked this bug as a duplicate of the following bug]

[UG] Missing disclaimer for Linux users

Note from the teaching team: This bug was reported during the Part II (Evaluating Documents) stage of the PE. You may reject this bug if it is not related to the quality of documentation.

Description

Quick start section includes a disclaimer for MacOS users to download an external data.zip file. This same warning is missing for Linux, which similarly run Unix.

I suspect this missing information is what leads to init and display command failures for Linux users.

[original: nus-cs2113-AY2324S2/pe-interim#2479] [original labels: severity.Medium type.DocumentationBug]

Their Response to the 'Original' Bug

[This is the team's response to the above 'original' bug]

Thank you for pointing this out. This does indeed cause problems for Linux users.

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)

Reason for disagreement: To qualify as a duplicate, it must be impossible for both issues to be fixed independently. However the fact that the 'original' exists in documentation while this exists in the application (code) strongly suggests that they can.

For example, programming display to work without external dependencies while still leaving some part of the application reliant on data.zip would fix this issue but not the other.

## :question: Issue type Team chose [`type.DocumentationBug`] Originally [`type.FunctionalityBug`] - [x] I disagree **Reason for disagreement:** This is clearly a functionality that does not work as expected, i.e. `FunctionalityBug`
## :question: Issue severity Team chose [`severity.Medium`] Originally [`severity.High`] - [ ] I disagree **Reason for disagreement:** [replace this with your explanation]