```
bazel run //ci/official/requirements_updater:requirements.update --repo_env=HERMETIC_PYTHON_VERSION=3.12
```

where `3.12` is the `Python` version you wish to update.

Note, since it is still `pip` and `pip-compile` tools used under the hood, so
most of the command line arguments and features supported by those tools will be
acknowledged by the Bazel requirements updater command as well. For example, if

     * attributes are asserted here only because server file systems may not
     * support filtering by all attributes (e.g. even though ATTR_DIRECTORY was
     * specified the server may still return objects that are not directories).
     */
    @Override
    public boolean accept(final SmbFile file) throws SmbException {
        return (file.getAttributes() & this.attributes) != 0;
    }

   * see calls in Google code that pass a null `dir` to a FilenameFilter.... So let's declare the
   * parameter as non-nullable (since passing null to a FilenameFilter is unsafe in general), but if
   * someone still manages to pass null, let's continue to have the method work.
   *
   * (PatternFilenameFilter is of course one of those classes that shouldn't be a publicly visible

        id("${model.projectId}_TestPerformanceTest")
        name = "Test performance test tasks - Java8 Linux"
        description = "Tries to run an adhoc performance test without a database connection to verify this is still working"

        applyPerformanceTestSettings()
        artifactRules = INDIVIDUAL_PERFORAMCE_TEST_ARTIFACT_RULES

        steps {
            killProcessStep(buildTypeThis, KILL_ALL_GRADLE_PROCESSES, os)

        assertEquals(0, bytesWritten, "Should return 0 bytes written for null source.");
        assertEquals(pos, NtlmMessage.readULong(dest, off), "Position should still be written for null source.");

        // Test with empty source array
        dest = new byte[20];
        bytesWritten = NtlmMessage.writeSecurityBufferContent(dest, pos, off, new byte[0]);

 * rarely use it directly, in part because it does not provide direct access to the {@code Future}
 * result. (If you want such access, you may prefer {@link Futures#addCallback
 * Futures.addCallback}.) Still, direct {@code addListener} calls are occasionally useful:
 *
 * {@snippet :
 * final String name = ...;
 * inFlight.add(name);
 * ListenableFuture<Result> future = service.query(name);

        assertEquals(8, bytesDecoded1); // Should still return 8
        assertEquals(expectedIndexNumber, fileInternalInfo.getIndexNumber());

        FileInternalInfo info2 = new FileInternalInfo();
        int bytesDecoded2 = info2.decode(buffer, 0, 15); // More than needed
        assertEquals(8, bytesDecoded2); // Should still return 8
        assertEquals(expectedIndexNumber, info2.getIndexNumber());
    }

So, you could add additional data to the automatically generated schema.

For example, you could decide to read and validate the request with your own code, without using the automatic features of FastAPI with Pydantic, but you could still want to define the request in the OpenAPI schema.

You could do that with `openapi_extra`:

{* ../../docs_src/path_operation_advanced_configuration/tutorial006.py hl[19:36, 39:40] *}

{* ../../docs_src/extra_models/tutorial001_py310.py hl[7,9,14,20,22,27:28,31:33,38:39] *}


/// info

In Pydantic v1 the method was called `.dict()`, it was deprecated (but still supported) in Pydantic v2, and renamed to `.model_dump()`.

The examples here use `.dict()` for compatibility with Pydantic v1, but you should use `.model_dump()` instead if you can use Pydantic v2.

///

 * rarely use it directly, in part because it does not provide direct access to the {@code Future}
 * result. (If you want such access, you may prefer {@link Futures#addCallback
 * Futures.addCallback}.) Still, direct {@code addListener} calls are occasionally useful:
 *
 * {@snippet :
 * final String name = ...;
 * inFlight.add(name);
 * ListenableFuture<Result> future = service.query(name);