docs: Document runsync client timeout behavior#585
Draft
promptless[bot] wants to merge 1 commit intomainfrom
Draft
docs: Document runsync client timeout behavior#585promptless[bot] wants to merge 1 commit intomainfrom
promptless[bot] wants to merge 1 commit intomainfrom
Conversation
![promptless[bot]](https://avatars.githubusercontent.com/in/979718?s=60&v=4){kind=small}
| ``` | ||
|
|
||
| <Note> | ||
| The Flash SDK's `runsync()` method uses your `execution_timeout_ms` value as the client-side HTTP timeout. If set to a positive value, the SDK waits that duration for the job to complete. If unset or set to `0`, the SDK defaults to a 60-second timeout. For long-running inference jobs, set `execution_timeout_ms` to prevent premature timeouts. |
Contributor
Author
There was a problem hiding this comment.
Citation: Bug fix PR that changed runsync() to use executionTimeoutMs / 1000 as client timeout instead of hardcoded 60s. Changes in src/runpod_flash/core/resources/serverless.py show the timeout derivation logic with guard for None and 0 values.
View source
| } | ||
| ``` | ||
|
|
||
| The `/runsync` endpoint has a 60-second client-side timeout by default. If you've configured `execution_timeout_ms` on your endpoint, the client timeout uses that value instead. For jobs that take longer than 60 seconds, set `execution_timeout_ms` to prevent `/runsync` requests from timing out. |
Contributor
Author
There was a problem hiding this comment.
Citation: PR #272 fixes ServerlessResource.runsync() to respect executionTimeoutMs for client-side HTTP timeout. The PR description explains the prior bug: 60s hardcoded timeout caused GPU inference jobs >1 minute to fail.
View source
|
Preview deployment for your docs. Learn more about Mintlify Previews.
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Open this suggestion in Promptless to view citations and reasoning process
Documents that the Flash SDK's
runsync()method usesexecution_timeout_msas the client-side HTTP timeout. This clarifies that long-running jobs (>60 seconds) needexecution_timeout_msconfigured to prevent client-side timeouts.Trigger Events
runpod/flash PR #272: fix(serverless): use executionTimeoutMs as runsync client timeout
Promptless Research (5 files, 1 GitHub PR)
.long_term_context/product_knowledge/product_overview.md.long_term_context/doc_workflow/client_instructions.mdflash/configuration/parameters.mdxflash/apps/requests.mdx.long_term_context/style/client_style_guide.mdAgent Response
Tip: Point @Promptless at some of your docs debt and have it clean them up in the background 🧹