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

provider-services client: http_options limits are too strict, cannot set values beyond the defaults #247

Open
andy108369 opened this issue Aug 12, 2024 · 1 comment
Assignees
Labels
P2 repo/provider Akash provider-services repo issues

Comments

@andy108369
Copy link
Contributor

andy108369 commented Aug 12, 2024

The read_timeout is 60s by default,
and I cannot set it to a larger value as provider-services client exits with this error:

Error: http option not allowed: read timeout cannot be greater than 60000 ms
  • SDL:

changed 60 to 61 seconds

    expose:
      - port: 80
        as: 80
        to:
          - global: true
        accept:
          - api-andy1.beta.akashml.com
        http_options:
          read_timeout: 61000

I believe these limits are the same for the send_timeout, and next_timeout as well.

provider-services v0.6.2

Additional information

Console UI doesn't seem to be restricting this as I've seen people were setting http_options.read_timeout to much larger values such as 600000 (600 seconds); yet hitting another issue

@andy108369
Copy link
Contributor Author

andy108369 commented Aug 13, 2024

Looks like the same restriction for max_body_size http_options param in SDL

CLI:

Error: http option not allowed: body size cannot be greater than 104857600 bytes

@chainzero chainzero added repo/provider Akash provider-services repo issues P2 and removed awaiting-triage labels Aug 21, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
P2 repo/provider Akash provider-services repo issues
Projects
None yet
Development

No branches or pull requests

3 participants