Prevent gradio_client from sending out of range value for gr.Slider

[hysts]

• I have searched to see if a similar issue already exists.

When using gr.Slider, users can restrict the possible input values with minimum, maximum, step. For example, we can limit the value to multiples of 5 from 0 to 100 by doing gr.Slider(minimum=0, maximum=100, step=5, value=0), but currently Client can send arbitrary values, like 1000000 or 1.23, ignoring this restriction.
This is problematic, for example, when the batch size is set with gr.Slider. Client can send a value like 100, which would probably cause GPU OOM and crash the Space. Once GPU OOM occurs, a Space will stop working properly until manually restarted.
I guess Space developers can add some logic in their functions to reject unacceptable values, but it will increase their work. So, it would be nice if it was taken care of on gradio side.

[freddyaboulton]

I don't think the best fix is at the client level. Even if you set steps in the app, the front-end won't prevent you from typing a value for the slider that's out of range or incorrect precision.

I think the better approach is to tackle #2718 and then if the client sends a request with an invalid value it will automatically fail.

[hannahblair]

Removing the gradio_client tag in light of @freddyaboulton's comment