/** Injected search engine client for OpenSearch operations. */
    @Resource
    protected SearchEngineClient searchEngineClient;

    /** Injected helper for web and file system indexing operations. */
    @Resource
    protected WebFsIndexHelper webFsIndexHelper;

    /** Injected helper for data store indexing operations. */
    @Resource

 * specific language governing permissions and limitations
 * under the License.
 */
package org.apache.maven.repository.metadata;

import javax.inject.Inject;
import javax.inject.Named;
import javax.inject.Singleton;

import java.util.ArrayList;
import java.util.List;
import java.util.TreeSet;

import org.apache.maven.artifact.ArtifactScopeEnum;

/**

        // Test SearchEngineClient field injection
        ThumbnailGenerator generator = new ThumbnailGenerator();
        assertNull(generator.searchEngineClient);

        // After proper initialization, it should be injected
        SearchEngineClient mockClient = new SearchEngineClient() {
            // Mock implementation
        };
        generator.searchEngineClient = mockClient;

    /**
     * Helper method to create a DcerpcPipeHandle with injected mocks
     * Uses mock to avoid constructor issues while allowing real method calls
     */
    private DcerpcPipeHandle createMockedDcerpcPipeHandle() throws Exception {
        // Create a mock without calling the constructor
        DcerpcPipeHandle handle = mock(DcerpcPipeHandle.class);

        // Inject the binding using reflection

Only the code prior to and including the `yield` statement is executed before creating a response:

{* ../../docs_src/dependencies/tutorial007.py hl[2:4] *}

The yielded value is what is injected into *path operations* and other dependencies:

{* ../../docs_src/dependencies/tutorial007.py hl[4] *}

The code following the `yield` statement is executed after creating the response but before sending it:

In fact, those blocks of code are not written inside the Markdown, they are Python files in the `./docs_src/` directory.

And those Python files are included/injected in the documentation when generating the site.

### Docs for tests

Most of the tests actually run against the example source files in the documentation.

This helps to make sure that:

        assertFalse(filter.accept(smbFile), "Negative size should be rejected");
        verify(smbFile, times(1)).length();

        // zero size -> reject
        reset(smbFile);
        when(smbFile.length()).thenReturn(0L);
        assertFalse(filter.accept(smbFile), "Zero size should be rejected");
        verify(smbFile, times(1)).length();

        // positive size -> accept

 * specific language governing permissions and limitations
 * under the License.
 */
package org.apache.maven.repository.metadata;

import javax.inject.Inject;
import javax.inject.Named;
import javax.inject.Singleton;

import java.util.ArrayList;
import java.util.Arrays;
import java.util.List;

import org.apache.maven.artifact.ArtifactScopeEnum;

/**

            "48, 32, true", // DIRECTORY | ARCHIVE vs ARCHIVE
            "21, 5, true", // READONLY | SYSTEM | DIRECTORY vs READONLY | SYSTEM

            // Negative cases (should be rejected)
            "1, 2, false", // READONLY vs HIDDEN
            "2, 1, false", // HIDDEN vs READONLY
            "16, 32, false", // DIRECTORY vs ARCHIVE
            "3, 4, false", // READONLY | HIDDEN vs SYSTEM

        for (int i = 0; i < 8; i++) {
            baos.write((int) ((value >> (i * 8)) & 0xFF));
        }
    }

    @Test
    void testEmptyPac() {
        // Test that PAC with size <= 8 is rejected
        byte[] emptyData = new byte[8];

        PACDecodingException e = assertThrows(PACDecodingException.class, () -> new Pac(emptyData, keys));
        // Any PACDecodingException is acceptable for this test