-
Notifications
You must be signed in to change notification settings - Fork 3k
test(e2e): stabilize managed startup recovery #7975
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
Merged
Changes from 2 commits
Commits
Show all changes
3 commits
Select commit
Hold shift + click to select a range
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
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
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
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
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 | 🟡 Minor | ⚡ Quick win
🧩 Analysis chain
🏁 Script executed:
Repository: NVIDIA/NemoClaw
Length of output: 29840
🏁 Script executed:
Repository: NVIDIA/NemoClaw
Length of output: 36640
🌐 Web query:
Official curl documentation for --retry, --retry-all-errors, --fail, and the minimum curl version for --retry-all-errors💡 Result:
The official documentation for curl provides several options for managing transfer failures and retries [1][2]. The following details summarize these options and their behavior: --retry Normally, curl performs a single attempt and returns an error if it fails. This option specifies the number of times curl should retry a transfer if a transient error occurs [1]. Transient errors include timeouts, FTP 4xx response codes, and HTTP 408, 429, 500, 502, 503, or 504 response codes [1]. By default, curl does not retry (0 attempts) [1]. --retry-all-errors This option, introduced in curl 7.71.0, is a more aggressive form of retrying that tells curl to treat all transfer failures as a reason to retry, rather than just transient errors [1][3][4]. It must be used in conjunction with --retry [3][5]. It is considered a sledgehammer approach and users are warned that it may cause unintended consequences, such as receiving duplicate data, especially when used with redirected output [3][5]. --fail (HTTP) This option tells curl to fail silently with an error code (22) and no response body when an HTTP server returns an error code of 400 or greater [2][6]. It is useful for detecting server errors that might otherwise be ignored if the transfer itself completes [3][5]. It can be combined with --retry and --retry-all-errors to ensure that HTTP errors (4xx and 5xx) trigger a retry [3][5]. Minimum Version for --retry-all-errors The --retry-all-errors option was added in curl version 7.71.0 [3][4][7].
Citations:
🏁 Script executed:
Repository: NVIDIA/NemoClaw
Length of output: 866
Align the retry policy with the stated contract.
--retry 3permits three retries after the initial transfer, so each asset can receive four attempts. With-f,--retry-all-errorsalso retries HTTP failures such as missing release assets.If three total attempts are required, use
--retry 2and remove--retry-all-errors. Retain--retry-all-errorsonly when supported installer hosts provide curl 7.71.0 or newer.🤖 Prompt for AI Agents