You can use the same dependency *functions* you use normally.

### Dependency requirements { #dependency-requirements }

They can declare request requirements (like headers) or other sub-dependencies:

{* ../../docs_src/dependencies/tutorial006_an_py39.py hl[8,13] *}

### Raise exceptions { #raise-exceptions }

        long elapsed = endTime - startTime;
        assertTrue("Expected at least 15ms sleep, got " + elapsed + "ms", elapsed >= 15);
        // Generous tolerance for CI environments like GitHub Actions
        assertTrue("Expected less than 200ms sleep, got " + elapsed + "ms", elapsed < 200);
    }

    public void test_waitForNext_withZeroInterval() {
        configHelper.setReloadInterval(0L);

echo. 1>&2
echo Please set the JAVA_HOME variable in your environment to match the 1>&2
echo location of your Java installation. 1>&2

goto fail

:execute
@rem Setup the command line

set CLASSPATH=


@rem Execute Gradle
"%JAVA_EXE%" %DEFAULT_JVM_OPTS% %JAVA_OPTS% %GRADLE_OPTS% "-Dorg.gradle.appname=%APP_BASE_NAME%" -classpath "%CLASSPATH%" -jar "%APP_HOME%\gradle\wrapper\gradle-wrapper.jar" %*

    text(
        "profiler",
        defaultProfiler,
        display = ParameterDisplay.PROMPT,
        allowEmpty = false,
        description =
            "Command line option for the performance test task to enable profiling. " +
                "For example `async-profiler`, `async-profiler-heap`, `async-profiler-all` or `jfr`. Use `none` for benchmarking only.",
    )
}

l/58171), [@verult](https://github.com/verult))

* Default values differ between the Kubelet's componentconfig (config file) API and the Kubelet's command line. Be sure to review the default values when migrating to using a config file. For example, the authz mode is set to "AlwaysAllow" if you rely on the command line, but defaults to the more secure "Webhook" mode if you load config from a file. ([#59666](https://github.com/kubernetes/kubernetes/pull/59666), [@mtaufen](https://github.com/mtaufen))...

     * Default constructor.
     */
    public NotificationHelper() {
        // Default constructor
    }

    private static final Logger logger = LogManager.getLogger(NotificationHelper.class);

    /** Line feed character for message formatting. */
    protected static final char LF = '\n';

    /**
     * Sends notifications to configured platforms.
     *
     * @param cardView the card view for the notification

  interface ItemReporter {
    String reportItem(Item<?> item);
  }

  /**
   * A word about using {@link Equivalence}, which automatically checks for {@code null} and
   * identical inputs: This sounds like it ought to be a problem here, since the goals of this class
   * include testing that {@code equals()} is reflexive and is tolerant of {@code null}. However,

* etc.

{* ../../docs_src/response_status_code/tutorial001.py hl[6] *}

/// note

Notice that `status_code` is a parameter of the "decorator" method (`get`, `post`, etc). Not of your *path operation function*, like all the parameters and body.

///

The `status_code` parameter receives a number with the HTTP status code.

/// info

    }

    // Test reload with invalid format
    public void test_reload_invalidFormat() throws Exception {
        writeTestFile("a,b => c\ninvalid_line\nd,e => f\n");

        // Should skip invalid line
        PagingList<CharMappingItem> result = charMappingFile.selectList(0, 10);
        assertEquals(2, result.size());
    }

    // Test reload with missing arrow

 *
 * 2. The supertype of this class could be `Function<@Nullable A, @Nullable B>`, since
 * Converter.apply (like Converter.convert) is capable of accepting null inputs. However, a
 * supertype of `Function<A, B>` turns out to be massively more useful to callers in practice: They
 * want their output to be non-null in operations like `stream.map(myConverter)`, and we can