* suggests MS doesn't compute the signature (correctly) for error responses
         * (perhaps for DOS reasons).
         */
        /*
         * Looks like the failure case also is just reflecting back the signature we sent
         */

        /**
         * Maybe this is related:
         *

// parseRestoreObjStatus parses restoreHdr from AmzRestore header. If the value is valid it returns a
// restoreObjStatus value with the status and expiry (if any). Otherwise returns
// the empty value and an error indicating the parse failure.
func parseRestoreObjStatus(restoreHdr string) (restoreObjStatus, error) {
	tokens := strings.SplitN(restoreHdr, ",", 2)
	progressTokens := strings.SplitN(tokens[0], "=", 2)
	if len(progressTokens) != 2 {

labels.dict_stopwords_details=Dict Stopwords 詳情
labels.dict_synonym_details=Dict Synonym 詳情
labels.duplicate_host_details=Duplicate Host 詳情
labels.elevate_word_details=Elevate Word 詳情
labels.failure_url_details=Failure Url 詳情
labels.file_auth_details=File Auth 詳情
labels.file_config_details=File Config 詳情
labels.group_details=Group 詳情
labels.job_log_details=Job Log 詳情
labels.key_match_details=Key Match 詳情

        Request
          .Builder()
          .url(server.url("/"))
          .build(),
      )
    val response = call.execute()
    if (expectedProtocol == Protocol.HTTP_2) {
      // soft failure since client may not support depending on Platform
      assumeThat(response, matchesProtocol(Protocol.HTTP_2))
    }
    assertThat(response.protocol).isEqualTo(expectedProtocol)
    assertFailsWith<IOException> {

		}
		if checkCopyObjectPartPreconditions(ctx, w, r, o) {
			return true
		}
		if parseRangeErr != nil {
			writeCopyPartErr(ctx, w, parseRangeErr, r.URL)
			// Range header mismatch is pre-condition like failure
			// so return true to indicate Range precondition failed.
			return true
		}
		return false
	}
	getOpts.CheckPrecondFn = checkCopyPartPrecondFn

labels.dict_stopwords_details=Dict Stopwords विवरण
labels.dict_synonym_details=Dict Synonym विवरण
labels.duplicate_host_details=Duplicate Host विवरण
labels.elevate_word_details=Elevate Word विवरण
labels.failure_url_details=Failure Url विवरण
labels.file_auth_details=File Auth विवरण
labels.file_config_details=File Config विवरण
labels.group_details=Group विवरण
labels.job_log_details=Job Log विवरण
labels.key_match_details=Key Match विवरण

                    try {
                        response = trans.send(request, response, params);
                    } catch (SmbException e) {
                        // Handle potential multi-channel failure
                        if (isUseMultiChannel() && trans != this.transport) {
                            ChannelInfo channel = channelManager.getChannelForTransport(trans);
                            if (channel != null) {

Unfortunately, there is a much rarer second possible failure mode: the replication controller gets renamed to the old name, but there is a duplicated set of pods in the cluster. kubectl will not report an error since it thinks its job is done.

	"github.com/minio/minio/internal/hash/sha256"
	xhttp "github.com/minio/minio/internal/http"
	ioutilx "github.com/minio/minio/internal/ioutil"
)

// Type to capture different modifications to API request to simulate failure cases.
type Fault int

const (
	None Fault = iota
	MissingContentLength
	TooBigObject
	TooBigDecodedLength
	BadSignature
	BadMD5
	MissingUploadID
)

   * ensure type safety. For best results, use the standard method-chaining idiom illustrated in the
   * class documentation above, configuring a builder and building your cache in a single statement.
   * Failure to heed this advice can result in a {@link ClassCastException} being thrown by a cache
   * operation at some <i>undefined</i> point in the future.
   *