Skip to content

Conversation

kt474
Copy link
Member

@kt474 kt474 commented Sep 4, 2025

Summary

Adding client side validation to make sure rep_delay value is within the backend's rep_delay_range.

Details and comments

Fixes #2387

@kt474 kt474 added the Changelog: New Feature Include in the Added section of the changelog label Sep 4, 2025
if rep_delay < rep_delay_range[0] or rep_delay > rep_delay_range[1]:
raise ValueError(
f"rep_delay {rep_delay} is not in the backend rep_delay_range {rep_delay_range}"
)
Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I didn't want to repeat this code but I don't think there's a way to do this directly in the ExecutionOptions because we need to check the backend config for the rep_delay_range

Copy link
Collaborator

@ElePT ElePT left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I am in favor of having checks, but I am wondering which validations should be the client's responsibility and which should be the validation service's responsibility. I would have expected this to be one of the parameters checked in the validation process. I think that the overall pipeline should be synchronized a bit better.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Changelog: New Feature Include in the Added section of the changelog
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Check rep_delay value during submission of a job
2 participants