}
                return false;
            }

            private boolean isChildOf(final File directory, final File file) {
                return file.toPath().startsWith(directory.toPath());
            }

            private boolean isSymbolicLink(final FileCopyDetailsInternal details) {
                final File file;
                try {

    └── swagger-ui.css
```

### Die statischen Dateien bereitstellen { #serve-the-static-files }

* Importieren Sie `StaticFiles`.
* „Mounten“ Sie eine `StaticFiles()`-Instanz in einem bestimmten Pfad.

{* ../../docs_src/custom_docs_ui/tutorial002_py310.py hl[7,11] *}

### Die statischen Dateien testen { #test-the-static-files }

    The problem is that GWT responds poorly to two .gwt.xml files in the same
    Java package; see
    https://groups.google.com/g/google-web-toolkit-contributors/c/CqYH59Dt_rQ/m/uVGW1QdUsXUJ
    for details.

    The summary is that it ignores one file in favor of the other.
    util.concurrent, like nearly all our packages, has two .gwt.xml files: one
    for prod and one for tests. However, unlike our other packages, as of this

# Treat all files in the Go repo as binary, with no git magic updating
# line endings. This produces predictable results in different environments.
#
# Windows users contributing to Go will need to use a modern version
# of git and editors capable of LF line endings.
#
# Windows .bat files are known to have multiple bugs when run with LF
# endings, and so they are checked in with CRLF endings, with a test

import org.codelibs.fess.dict.DictionaryFile;
import org.codelibs.fess.dict.DictionaryItem;

import jakarta.annotation.PostConstruct;

/**
 * A dictionary creator for stopwords files.
 * This class is responsible for creating {@link StopwordsFile} instances
 * from files that match the pattern "stopwords.*\\.txt".
 */
public class StopwordsCreator extends DictionaryCreator {

            final Consumer<SearchRequestBuilder> cb = builder -> {
                final QueryBuilder queryBuilder = QueryBuilders.boolQuery()
                        .filter(QueryBuilders.termsQuery(OpenSearchAccessResult.SESSION_ID, sessionIdList))
                        .filter(QueryBuilders.termQuery(OpenSearchAccessResult.STATUS, org.codelibs.fess.crawler.Constants.OK_STATUS));
                builder.setQuery(queryBuilder);

```
(You can paste links or attach files by dragging & dropping them below)
- Provide links to your updated versions of the above two colab notebooks.
- Provide links to your TensorFlow model and (optionally) TensorFlow Lite Model.
```

#### Option B: Paste your code here or provide a link to a custom end-to-end colab

```
(You can paste links or attach files by dragging & dropping them below)

        }

        // user
        file = context.userHomeDirectory.resolve(eff.get(Constants.MAVEN_USER_EXTENSIONS));
        loaded = readCoreExtensionsDescriptorFromFile(file, true);
        if (!loaded.isEmpty()) {
            result.add(new CoreExtensions(file, loaded));
        }

        // installation

     * Sets up the database query conditions for listing crawling information records.
     * Applies filters based on the pager criteria such as ID and session ID,
     * and orders results by creation time in descending order.
     *
     * @param cb the condition bean for building the database query
     * @param crawlingInfoPager the pager containing filter criteria
     */

import org.codelibs.fess.dict.DictionaryFile;
import org.codelibs.fess.dict.DictionaryItem;

import jakarta.annotation.PostConstruct;

/**
 * A dictionary creator for synonym files.
 * This class is responsible for creating {@link SynonymFile} instances
 * from files that match the pattern "synonym.*\\.txt".
 */
public class SynonymCreator extends DictionaryCreator {
    private static final Logger logger = LogManager.getLogger(SynonymCreator.class);