We create an `HTTPException` that we can reuse (`raise`) later at several points.

In this exception, we include the scopes required (if any) as a string separated by spaces (using `scope_str`). We put that string containing the scopes in the `WWW-Authenticate` header (this is part of the spec).

    }

    val bucketProvider = when {
        parameters.includeTestClasses.get().isNotBlank() -> {
            val content = parameters.repoRoot.file("test-splits/include-test-classes.properties").get().asFile.readText()
            println("Tests to be included:\n$content")
            IncludeTestClassProvider(readTestClasses(content))
        }
        parameters.excludeTestClasses.get().isNotBlank() -> {

        return new RelevanceEvaluationResult(Collections.emptyList(), Collections.emptyList(), false);
    }

    /**
     * Creates a fallback result that includes all documents as relevant.
     * Used when evaluation fails and we want to include all search results.
     *
     * @param allDocIds all document IDs from search results
     * @return evaluation result with all documents marked as relevant
     */

    }

    @Test
    void testPopulateWithIncludeDirective() throws Exception {
        // Test that #INCLUDE directive is handled (even if the include fails)
        String content = "#INCLUDE \\\\server\\share\\lmhosts\n" + "192.168.1.100 MAINHOST\n";

        // Mock SmbFileInputStream to simulate include file
        try (MockedConstruction<SmbFileInputStream> mockedConstruction =

may include command line options.

The cgo tool will always invoke the C compiler with the source file's
directory in the include path; i.e. -I${SRCDIR} is always implied. This
means that if a header file foo/bar.h exists both in the source
directory and also in the system include directory (or some other place
specified by a -I flag), then "#include <foo/bar.h>" will always find the

    private FileTree sources;
    /**
     * Directories to include notices from
     */
    private List<File> licensesDirs = new ArrayList<File>();

    public NoticeTask() {
        setDescription("Create a notice file from dependencies");
        // Default licenses directory is ${projectDir}/licenses (if it exists)

        shutil.copy2(file_path, py310_file)


@app.command()
def update_docs_includes_py39_to_py310() -> None:
    """
    Update .md files in docs/en/ to replace _py39 includes with _py310 versions.

    For each include line referencing a _py39 file or directory in docs_src, replace
    the _py39 label with _py310.
    """
    include_pattern = re.compile(r"\{[^}]*docs_src/[^}]*_py39[^}]*\.py[^}]*\}")

You can combine `dataclasses` with other type annotations in many different combinations to form complex data structures.

Check the in-code annotation tips above to see more specific details.

## Learn More { #learn-more }

You can also combine `dataclasses` with other Pydantic models, inherit from them, include them in your own models, etc.

  build1 --> project2
  
  build2["included build"]
  build_tree --> build2
  
  project3["root project"]
  build2 --> project3
  
  project4["project"]
  build2 --> project4

```

### Build process state

The "build process state" holds the global state of the build process and manages all the other state.

The build process state also includes state that is tied to a particular Gradle user home directory.

// string is returned, then the driver type name is not supported.
// Consult your driver documentation for a list of driver data types. Length specifiers
// are not included.
// Common type names include "VARCHAR", "TEXT", "NVARCHAR", "DECIMAL", "BOOL",
// "INT", and "BIGINT".
func (ct ColumnType) DatabaseTypeName() string {
	if ct.DataTypeValue.Valid {
		return ct.DataTypeValue.String
	}