Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Investigate using the server defaults endpoint to preset ambiguous defaults #116

Open
cugarteblair opened this issue Oct 2, 2024 · 0 comments
Labels
enhancement New feature or request

Comments

@cugarteblair
Copy link
Contributor

The worker timeout is preset to 600 secs and is set to the request timeout if the request timeout was overrided by the user.

"I like the minimilist approach of not setting the parameter when it was not overridden by the user and relying on the server to preset. With this, I preset the values in my store to illegal values. That is my way of knowing the user did not override that value and therefore leave it out of the request.
We absolutely need to know exactly what the server used and getting that in the metadata of the file is imperative.
As opposed to the explicit approach I thought I would be using of using the defaults endpoint API to preset all the values and then explicitly set all the values in the request (not as good) and assume that is what the server used.
I will add another column to record so we can show request parms sent/overrided against request parms used.
So I won't use that defaults API for anything else besides the timeout, unless I am missing something."

@cugarteblair cugarteblair added the enhancement New feature or request label Oct 2, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant