chore: remove unneccessary WithFailFast option #4484
Merged
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.
WithFailFast
was not actually causing any change in behavior, so we can remove the option completely.The option set
FailOnNonTempDialError(true)
on the gRPC connection. However, the help text for this method option declares that it "does not do anything useful unless you are also usingWithBlock()
" - which we do not do. I've verified that the only client-side code path that actually handles this option is under a check for ifWithBlock()
was also used.We can remove this option instead of fixing it, since the need for this functionality has been replaced by the more buildkit-native client.Wait function - this function also correctly waits for the buildkit server to begin running, and to start serving requests (which is generally the desired behaviour).
If users actually desire this option (which was not fully working previously), they can use the
WithGRPCDialOption
, and passFailOnNonTempDialError(true)
directly, alongsideWithBlock
.