* resources
 *
 * We need to look at Maven, and Nexus as use cases and figure out what each of them needs to be
 * able to do
 *
 * - now what is really the difference between this and loading a component in plexus - custom
 * classloading capability - remote resolution of dependencies - do we want a model for sharing
 * information among plugins, is this more like an extension point - do we need a sort of bus for

.Values.configPathmc }}certs {{ end }} resources: {{ toYaml .Values.makeUserJob.resources | indent 10 }} {{- end }} minio/templates/post-install-custom-command.yaml {{- if .Values.customCommands }} apiVersion: batch/v1 kind: Job metadata: name: {{ template "minio.fullname" . }}-custom-command-job namespace: {{ .Release.Namespace | quote }} labels: app: {{ template "minio.name" . }}-custom-command-job chart: {{ template "minio.chart" . }} release: {{ .Release.Name }} heritage: {{ .Release.Service }} annotations: "helm.sh/hook":...

nindent 10 }} {{- end }} resources: {{ toYaml .Values.makeUserJob.resources | indent 10 }} {{- end }} minio/templates/post-install-custom-command.yaml {{- if .Values.customCommands }} apiVersion: batch/v1 kind: Job metadata: name: {{ template "minio.fullname" . }}-custom-command-job namespace: {{ .Release.Namespace | quote }} labels: app: {{ template "minio.name" . }}-custom-command-job chart: {{ template "minio.chart" . }} release: {{ .Release.Name }} heritage: {{ .Release.Service }} annotations: "helm.sh/hook":...

  dependencies:
    path-key "^3.1.0"
    shebang-command "^2.0.0"
    which "^2.0.1"

custom-event@~1.0.0:
  version "1.0.1"
  resolved "https://registry.yarnpkg.com/custom-event/-/custom-event-1.0.1.tgz#5d02a46850adf1b4a317946a3928fccb5bfd0425"
  integrity sha512-GAj5FOq0Hd+RsCGVJxZuKaIDXDf3h6GQoNEjFgbLLI/trgtavwUbSnZ5pVfg27DVCaWjIohryS0JFwIJyT2cMg==

.Values.configPathmc }}certs {{ end }} resources: {{ toYaml .Values.makeUserJob.resources | indent 10 }} {{- end }} minio/templates/post-install-custom-command.yaml {{- if .Values.customCommands }} apiVersion: batch/v1 kind: Job metadata: name: {{ template "minio.fullname" . }}-custom-command-job namespace: {{ .Release.Namespace | quote }} labels: app: {{ template "minio.name" . }}-custom-command-job chart: {{ template "minio.chart" . }} release: {{ .Release.Name }} heritage: {{ .Release.Service }} annotations: "helm.sh/hook":...

     *
     * The server’s TLS certificate still must match the requested hostname. For example, if the
     * certificate is issued to `example.com` and the request is to `localhost`, the connection will
     * fail. Use a custom [HostnameVerifier] to ignore such problems.
     *
     * Other TLS features are still used but provide no security benefits in absence of the above

 * </ul>
 *
 * <p>The {@link TextNormalizeContext} class provides a fluent API to configure the text
 * normalization process, including setting initial buffer capacity, maximum term sizes,
 * duplicate term removal, and custom space characters.
 *
 * <p>Example usage:
 * <pre>{@code
 * Reader reader = new StringReader("Example text to normalize.");
 * String normalizedText = TextUtil.normalizeText(reader)

        // Note: getType() method does not exist in Type1Message
        assertTrue(type1.getFlags() != 0); // Should have some flags set
    }

    @Test
    @DisplayName("Should create Type 1 message with custom flags")
    void testType1MessageWithFlags() {
        // Given
        int flags =
                NtlmFlags.NTLMSSP_NEGOTIATE_UNICODE | NtlmFlags.NTLMSSP_NEGOTIATE_NTLM | NtlmFlags.NTLMSSP_NEGOTIATE_OEM_DOMAIN_SUPPLIED;

До FastAPI 0.106.0 вызывать исключения после `yield` было невозможно: код после `yield` в зависимостях выполнялся уже после отправки ответа, поэтому [Обработчики исключений](../tutorial/handling-errors.md#install-custom-exception-handlers){.internal-link target=_blank} к тому моменту уже отработали.

  /*
   * Under Android, MyError propagates up and fails the test?
   *
   * TODO(b/218700094): Does this matter to prod users, or is it just a feature of our testing
   * environment? If the latter, maybe write a custom Executor that avoids failing the test when it
   * sees an Error?
   */
  @AndroidIncompatible
  public void testTaskThrowsError() throws Exception {
    class MyError extends Error {}