search

myang2020 / pe

0 stars 0 forks source link

Unable to use or test delete timing command due to bug in <day> format #7

Open myang2020 opened 6 months ago

myang2020 commented 6 months ago

Copied the example command from the UG for the "delete_timing" command but am unable to use it due to the error shown in the screenshot.

Screen Shot 2024-04-19 at 4.41.40 pm.png

nus-se-script commented 5 months ago

Team's Response

Thanks for the report. However, we are unable to reproduce this bug. Steps taken to reproduce

  1. Start with a clean slate by deleting the data folder
  2. add_module i/1 m/cs2103t
  3. delete_timing i/1 m/cs2103t d/Mon st/0900 et/1000

The above commands was able to run successfully. We've tried to reproduce this with all the different dates from (Mon-Sun), using the error message dates as reference and ran successfully.

It would be great if you can provide the logs of the application and the system information such as the Operating System and the default OS language. We also attempted to change our system language in an attempt to reproduce but this was also to no avail.

Marked as a duplicate of #5500 since the bugs can not be fixed independently.

image.png

The 'Original' Bug

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

Unable to use or test "find_free_time" command due to bug in

I copied the exact sample command from the UG but still am unable to run this command due to a supposed error in the date format.

Screen Shot 2024-04-19 at 4.38.39 pm.png

[original: nus-cs2103-AY2324S2/pe-interim#5428] [original labels: type.FunctionalityBug severity.High]

Their Response to the 'Original' Bug

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

Thanks for the report. However, we are unable to reproduce this bug. Steps taken to reproduce

  1. Start with a clean slate by deleting the data folder
  2. find_free_time d/Mon st/1200 et/1300

The above commands was able to run successfully. We've tried to reproduce this with all the different dates from (Mon-Sun), using the error message dates as reference and ran successfully. We also attempted to change our system language in an attempt to reproduce but this was also to no avail. The above steps were taken on a Windows system, an M1 MacOS system and an M2 MacOS system.

It would be great if you can provide the logs of the application and the system information such as the Operating System and the default OS language

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: [replace this with your explanation]

## :question: Issue response Team chose [`response.CannotReproduce`] - [ ] I disagree **Reason for disagreement:** [replace this with your explanation]
## :question: Issue severity Team chose [`severity.Low`] Originally [`severity.High`] - [ ] I disagree **Reason for disagreement:** [replace this with your explanation]