You can configure some extra <a href="https://swagger.io/docs/open-source-tools/swagger-ui/usage/configuration/" class="external-link" target="_blank">Swagger UI parameters</a>.

To configure them, pass the `swagger_ui_parameters` argument when creating the `FastAPI()` app object or to the `get_swagger_ui_html()` function.

`swagger_ui_parameters` receives a dictionary with the configurations passed to Swagger UI directly.

        Throwable cause = new IllegalArgumentException("Invalid argument");
        GsaConfigException exception = new GsaConfigException(null, cause);

        assertNotNull(exception);
        assertNull(exception.getMessage());
        assertNotNull(exception.getCause());
        assertEquals(cause, exception.getCause());
        assertEquals("Invalid argument", exception.getCause().getMessage());
    }

     * This type can appear in the return value of a call to
     * {@link Session#resolveDependencies resolveDependencies(...)} when at least one dependency
     * cannot be associated to any type specified in the {@code desiredTypes} argument.
     * Plugins can choose to report a warning to users when unresolved paths exist.
     */
    PathType UNRESOLVED = new PathType() {
        @Override
        public String name() {
            return "UNRESOLVED";

        return null;
    }

    @Override
    public void fetchFirst(int fetchSize) {
        _fetchScopeEffective = true;
        if (fetchSize < 0) {
            String msg = "Argument[fetchSize] should be plus: " + fetchSize;
            throw new IllegalArgumentException(msg);
        }
        _fetchStartIndex = 0;
        _fetchSize = fetchSize;
        _fetchPageNumber = 1;

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
you wish the updater to consider pre-release versions simply pass `--pre`
argument to the bazel command:

```

        // When
        RuntimeCIFSException exception = new RuntimeCIFSException(cause);

        // Then
        assertNotNull(exception);
        assertEquals(cause, exception.getCause());
        assertTrue(exception.getMessage().contains("IllegalArgumentException"));
        assertTrue(exception.getMessage().contains("Invalid argument"));
    }

    @Test

    TF_AttrBuilder* builder, const char* device_type, TF_Status* status);

// For argument number input_index, fetch the corresponding number_attr that
// needs to be updated with the argument length of the input list.
// Returns nullptr if there is any problem like op_name is not found, or the
// argument does not support this attribute type.
TF_CAPI_EXPORT extern const char* TF_GetNumberAttrForOpListInput(

     * If either or both arrays have a length of {@literal 0}, the other array is returned as is.
     * In any case, the returned array is the same instance as the argument array and is not copied.
     * </p>
     *
     * @param <T>
     *            the type of the array elements
     * @param a
     *            first array
     * @param b
     *            second array

     * If that matcher returns {@code false}, then the directory will definitively not contain
     * the paths selected by the matcher given in argument to this method.
     * In such case, the whole directory and all its sub-directories can be skipped.
     * In case of doubt, or if the matcher given in argument is not recognized by this method,
     * then the matcher returned by this method will return {@code true}.
     *

        verify(signingDigest, times(5)).verify(any(byte[].class), anyInt(), anyInt(), anyInt(), any());
    }

    @Test
    @DisplayName("Test sign method invocation with argument capture")
    void testSignMethodArgumentCapture() {
        // Arrange
        ArgumentCaptor<byte[]> dataCaptor = ArgumentCaptor.forClass(byte[].class);