};

        SystemHelper systemHelper = new SystemHelper() {
            @Override
            public boolean isChangedClusterState(int status) {
                // Status 0 = GREEN is alive, should not show changed
                return false;
            }

            @Override
            public String getHostname() {
                return "test-hostname";
            }
        };

        crawlJob.fileConfigIds(null);
        crawlJob.dataConfigIds(null);

        String result = crawlJob.execute();

        assertNotNull(result);
        // When all configs are null, runAll is true, so they show ALL
        assertTrue(result.contains("Web  Config Id: ALL"));
        assertTrue(result.contains("File Config Id: ALL"));
        assertTrue(result.contains("Data Config Id: ALL"));
    }

                Customize the function used to generate unique IDs for the *path
                operations* shown in the generated OpenAPI.

                This is particularly useful when automatically generating clients or
                SDKs for your API.

                Read more about it in the
                [FastAPI docs about how to Generate Clients](https://fastapi.tiangolo.com/advanced/generate-clients/#custom-generate-unique-id-function).

But once you know the basic information of **HTTPS for developers** you can easily combine and configure different tools to help you manage everything in a simple way.

    // -----------------------------------------------------
    //                                            Entry Page
    //                                            ----------
    /**
     * Show the create new page.
     * @param dictId The dictionary ID.
     * @return The HTML response.
     */
    @Execute
    @Secured({ ROLE })
    public HtmlResponse createnew(final String dictId) {

An additional header `X-Minio-Replication-Delete-Status` is returned which would show `PENDING` or `FAILED` status if the replication is still not caught up.

The `scopes` parameter receives a `dict` with each scope as a key and the description as the value:

{* ../../docs_src/security/tutorial005_an_py310.py hl[63:66] *}

Because we are now declaring those scopes, they will show up in the API docs when you log-in/authorize.

And you will be able to select which scopes you want to give access to: `me` and `items`.

import junit.framework.TestCase;
import org.jspecify.annotations.NullUnmarked;

/**
 * Tests relating to cache expiration: make sure entries expire at the right times, make sure
 * expired entries don't show up, etc.
 *
 * @author mike nonemacher
 */
@SuppressWarnings("deprecation") // tests of deprecated method
@NullUnmarked
public class CacheExpirationTest extends TestCase {

#### Check the `openapi.json` { #check-the-openapi-json }

If you are curious about how the raw OpenAPI schema looks like, FastAPI automatically generates a JSON (schema) with the descriptions of all your API.

You can see it directly at: [http://127.0.0.1:8000/openapi.json](http://127.0.0.1:8000/openapi.json).

It will show a JSON starting with something like:

```JSON
{
    "openapi": "3.1.0",
    "info": {

            DfsReferralDataImpl result = DfsReferralDataImpl.fromReferral(mockReferral, "\\\\server\\share", pastExpiration, 10);

            assertEquals(pastExpiration, result.getExpiration());
            // toString should show negative remain time
            String str = result.toString();
            assertTrue(str.contains("remain="));
        }
    }