Description
The SLO target input fields (TTFT, ITL, E2E) in the specification editor enforce hard min/max limits based on the recommended range. If a user enters a value outside the range, Streamlit blocks it with a validation error (e.g., "Value must be less than or equal to 13300").
The recommended range should be advisory only — users should be free to enter any value they want. The range is a suggestion based on use-case defaults, not a hard constraint.
Current behavior
- E2E field shows "Recommended Range: 3500 - 13300 ms"
- Entering 14000 is blocked with "Value must be less than or equal to 13300"
Expected behavior
- Users can enter any positive value for SLO targets
- The recommended range is shown as guidance text only, not enforced
- The
st.number_input min/max parameters should not be set from the SLO range
Likely location
The st.number_input calls for SLO targets in the specification editor UI, probably using min_value and max_value from usecase_slo_workload.json ranges.
Description
The SLO target input fields (TTFT, ITL, E2E) in the specification editor enforce hard min/max limits based on the recommended range. If a user enters a value outside the range, Streamlit blocks it with a validation error (e.g., "Value must be less than or equal to 13300").
The recommended range should be advisory only — users should be free to enter any value they want. The range is a suggestion based on use-case defaults, not a hard constraint.
Current behavior
Expected behavior
st.number_inputmin/max parameters should not be set from the SLO rangeLikely location
The
st.number_inputcalls for SLO targets in the specification editor UI, probably usingmin_valueandmax_valuefromusecase_slo_workload.jsonranges.