-
-
Notifications
You must be signed in to change notification settings - Fork 85
RG-T131 Fixing TTS dockerfile #467
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
Merged
Changes from all commits
Commits
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
Oops, something went wrong.
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
🩺 Stability & Availability | 🟠 Major | ⚡ Quick win
🧩 Analysis chain
🏁 Script executed:
Repository: Resgrid/Core
Length of output: 1474
🏁 Script executed:
Repository: Resgrid/Core
Length of output: 5648
🌐 Web query:
curl official documentation --retry-max-time total time initial transfer retry semantics💡 Result:
The --retry-max-time option in curl is used to set a total time limit, in seconds, during which curl is permitted to perform retries [1][2]. Its semantics and interaction with other options are summarized below: Retry Timer Mechanics: The retry timer begins before the first transfer attempt [1][3]. The --retry-max-time value acts as a ceiling for the duration of the entire retry process [2][3]. Before starting any new retry attempt, curl checks if the elapsed time since the beginning of the initial attempt has exceeded this limit [4]. If the timer has reached or exceeded this limit, curl stops retrying and gives up [1][3]. Interaction with Transfer Duration: The --retry-max-time option only limits the time spent waiting for and initiating retries [2][3]. If a transfer attempt has already started and is currently in progress, it is permitted to complete even if its duration causes the total time to exceed the --retry-max-time limit [1][4]. To strictly limit the duration of each individual transfer attempt, you should use the --max-time option [5][1]. Inclusion of Wait Times: The retry timer includes both the time spent on actual transfer attempts and the time spent sleeping between attempts (e.g., due to the default exponential backoff or the --retry-delay option) [4]. Relationship with --retry: The --retry option defines the maximum number of times curl will retry a failed transfer [5][2]. The process will terminate when either the maximum number of retries defined by --retry is reached, or the duration defined by --retry-max-time has elapsed, whichever happens first [2]. If --retry-max-time is set to zero (the default), there is no time limit on retries [1][3].
Citations:
Limit retry time for every
curldownload.Add
--retry-max-time 600to the Piper archive, voice model, and metadata downloads. Keep--max-time 600because it limits each transfer attempt;--retry-max-timelimits the retry period. Without it, six attempts can allow one download to run for about 3,600 seconds.🤖 Prompt for AI Agents