// When
        int bytesRead = request.readBytesWireFormat(buffer, offset);

        // Then
        assertEquals(0, bytesRead);
    }

    @DisplayName("Should handle different completion filter combinations")
    @ParameterizedTest
    @CsvSource({ "1, FILE_NOTIFY_CHANGE_FILE_NAME", "2, FILE_NOTIFY_CHANGE_DIR_NAME", "4, FILE_NOTIFY_CHANGE_ATTRIBUTES",

import java.util.List;

/**
 * Holds a list of FtpAuthentication objects and provides methods to add and retrieve them based on a given path.
 * This class is designed to manage FTP authentication details for different paths.
 */
public class FtpAuthenticationHolder {
    List<FtpAuthentication> authenticationList = new ArrayList<>();

    /**
     * Constructs a new FtpAuthenticationHolder.
     */

## Include the same router multiple times with different `prefix` { #include-the-same-router-multiple-times-with-different-prefix }

You can also use `.include_router()` multiple times with the *same* router using different prefixes.

This could be useful, for example, to expose the same API under different prefixes, e.g. `/api/v1` and `/api/latest`.

   * Content-Type: text/html
   * Content-Length: 50
   * ```
   *
   * 2. Different order
   *
   * ```
   * Content-Length: 50
   * Content-Type: text/html
   * ```
   *
   * 3. Different case
   *
   * ```
   * content-type: text/html
   * content-length: 50
   * ```
   *
   * 4. Different values
   *
   * ```
   * Content-Type: text/html
   * Content-Length: 050

/// tip | 豆知識

テストに非同期関数呼び出しを統合した際に（例: [MongoDB の MotorClient](https://stackoverflow.com/questions/41584243/runtimeerror-task-attached-to-a-different-loop) 使用時）、`RuntimeError: Task attached to a different loop` に遭遇した場合は、イベントループを必要とするオブジェクトは非同期関数内でのみインスタンス化するようにしてください。例えば `@app.on_event("startup")` コールバック内で行います。

                        break;
                    }
                    /* Message was sent to WINS but
                     * failed to receive response.
                     * Try a different WINS server.
                     */
                    if (request.addr == NbtAddress.getWINSAddress()) {
                        NbtAddress.switchWINS();
                    }

            assertEquals(0, context.getSalt().length);
        }

        @ParameterizedTest
        @ValueSource(ints = { 0, 1, 3, 5, 10 })
        @DisplayName("Should calculate size correctly for different hash algo counts")
        void testSizeCalculation(int hashAlgoCount) {
            // Arrange
            int[] hashAlgos = new int[hashAlgoCount];
            byte[] salt = new byte[16];

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

/**
 * Tests our AtomicHelper fallback strategy in AggregateFutureState.
 *
 * <p>On different platforms AggregateFutureState uses different strategies for its core
 * synchronization primitives. The strategies are all implemented as subtypes of AtomicHelper and

     * null elements.
     *
     * @return the paths of all dependencies
     */
    @Nonnull
    List<Path> getPaths();

    /**
     * Returns the file paths of all dependencies and their assignments to different paths.
     * The {@link PathType} keys identify, for example, {@code --class-path} or {@code --module-path} options.
     * In the case of Java tools, the map may also contain {@code --patch-module} options, which are

   * {@linkplain Thread#getContextClassLoader() context class loader}. In simple environments, the
   * context class loader will find resources from the class path. In environments where different
   * threads can have different class loaders, for example app servers, the context class loader
   * will typically have been set to an appropriate loader for the current thread.
   *