logger.LogOnceIf(ctx, logSubsys, err, id, errKind...)
}

// ErrTargetsOffline - Indicates single/multiple target failures.
var ErrTargetsOffline = errors.New("one or more targets are offline. Please use `mc admin info --json` to check the offline targets")

// TestSubSysNotificationTargets - tests notification targets of given subsystem

* Fix for kube-proxy healthcheck handling an update that simultaneously removes one port and adds another. ([#44365](https://github.com/kubernetes/kubernetes/pull/44365), [@MrHohn](https://github.com/MrHohn))

       * We eliminate unnecessary node creation by catching cases where old nodes can be reused
       * because their next fields won't change. Statistically, at the default threshold, only
       * about one-sixth of them need cloning when a table doubles. The nodes they replace will be
       * garbage collectable as soon as they are no longer referenced by any reader thread that may
       * be in the midst of traversing table right now.

    assertThat(response.body.string()).isEqualTo("secure content")
  }

  /**
   * Verifies the null-handshake fix holds across multiple sequential cache writes, confirming
   * it is not a one-time race condition.
   *
   * https://github.com/square/okhttp/issues/8962
   */
  @Test
  fun multipleHttpsRequestsWithNullHandshakeAllSucceed() {
    server.useHttps(handshakeCertificates.sslSocketFactory())

  Now, when unschedulable Pods are updated, the scheduling queue checks with QueueingHint(s) whether the update may make the pods schedulable, and requeues them to activeQ/backoffQ **only when** at least one QueueingHint(s) return Queue. 
  
  Action required for custom scheduler plugin developers:

儘管如此，FastAPI 仍從 Requests 得到了不少啟發。

**Requests** 是一個「與 API 互動」（作為用戶端）的程式庫，而 **FastAPI** 是一個「建立 API」（作為伺服端）的程式庫。

它們大致位於相反兩端，彼此互補。

Requests 設計非常簡單直觀、容易使用，且有合理的預設值。同時它也非常強大且可自訂。

因此，如其官網所言：

> Requests is one of the most downloaded Python packages of all time

用法非常簡單。例如，發出一個 `GET` 請求，你會寫：

```Python
response = requests.get("http://example.com/some/url")
```

相對地，FastAPI 的 API 路徑操作（path operation）可能像這樣：

    return ImmutableList.copyOf(SORTED_NUMBER_NAMES.subList(i, j));
  }

  private static final ImmutableList<String> NUMBER_NAMES =
      ImmutableList.of("one", "two", "three", "four", "five", "six", "seven");

  private static final ImmutableList<String> SORTED_NUMBER_NAMES =
      Ordering.<String>natural().immutableSortedCopy(NUMBER_NAMES);

대략 말하면 서로 반대편에 있으며, 서로를 보완합니다.

Requests는 매우 단순하고 직관적인 설계를 가졌고, 합리적인 기본값을 바탕으로 사용하기가 아주 쉽습니다. 동시에 매우 강력하고 커스터마이징도 가능합니다.

그래서 공식 웹사이트에서 말하듯이:

> Requests is one of the most downloaded Python packages of all time

사용 방법은 매우 간단합니다. 예를 들어 `GET` 요청을 하려면 다음처럼 작성합니다:

```Python
response = requests.get("http://example.com/some/url")
```

in it, e.g. in a `List[Item]`), the Pydantic model class(es) will be a different one (the "cloned" one). So, an object that is a subclass won't simply pass the validation and returned as-is, because it is no longer a sub-class of the cloned `response_model`. Instead, a new Pydantic model object will be created with the contents of the returned object. So, it will be a new object (made with the data from the returned one), and will be filtered by the cloned `response_model`, containing only the declared...

	if err = verifyBinary(u, sha256Sum, releaseInfo, getMinioMode(), zr); err != nil {
		s.writeErrorResponse(w, err)
		return
	}
}

// CommitBinary - overwrites the current binary with the new one.
func (s *peerRESTServer) CommitBinaryHandler(w http.ResponseWriter, r *http.Request) {
	if !s.IsValid(w, r) {
		s.writeErrorResponse(w, errors.New("Invalid request"))
		return
	}