search

Austintjh19 / pe

0 stars 0 forks source link

Valuation prevents entry for 5 Trillion #9

Open Austintjh19 opened 1 month ago

Austintjh19 commented 1 month ago

image.png

In UG it mentions v/VALUATION to be a value between 0 and 5 Trillion. In the applicaiton it allows entry with a valuation of 0, as shown above, so one might think it is inclusive. However, the application actually prevents entry with valuation of 5 trillion, as shown below.

image.png

soc-se-bot commented 3 weeks ago

Team's Response

Within the constraint message, in the second screenshot you attached, the full message would have mentioned that the expected input for valuation is below 5 trillion, indicating the non-inclusivity. With this in mind, we do not think that this is a bug.

But we understand that we could have displayed this specification upfront or enhanced our error message to be better in the future, hence, we are opting for it to be NIS as per the guidelines given here.

Screenshot 2024-04-20 at 11.20.42 PM.png

Items for the Tester to Verify

:question: Issue response

Team chose [response.NotInScope]

Reason for disagreement: [replace this with your explanation]

## :question: Issue type Team chose [`type.FeatureFlaw`] Originally [`type.FunctionalityBug`] - [ ] I disagree **Reason for disagreement:** [replace this with your explanation]