submittingTaskQueue.nextTask = task;
          // requireNonNull(delegate) is safe for reasons similar to requireNonNull(sequencer).
          submittingTaskQueue.nextExecutor = requireNonNull(delegate);
          delegate = null;
        } else {
          // requireNonNull(delegate) is safe for reasons similar to requireNonNull(sequencer).
          Executor localDelegate = requireNonNull(delegate);

These status codes have a name associated to recognize them, but the important part is the number.

In short:

* `100 - 199` are for "Information". You rarely use them directly.  Responses with these status codes cannot have a body.
* **`200 - 299`** are for "Successful" responses. These are the ones you would use the most.

  /**
   * Not supported. Use {@link #naturalOrder}, which offers better type-safety, instead. This method
   * exists only to hide {@link ImmutableMultiset#builder} from consumers of {@code
   * ImmutableSortedMultiset}.
   *
   * @throws UnsupportedOperationException always
   * @deprecated Use {@link ImmutableSortedMultiset#naturalOrder}, which offers better type-safety.
   */
  @DoNotCall("Use naturalOrder.")
  @Deprecated

            assertTrue(RequestWithFileId.class.isAssignableFrom(impl), impl.getSimpleName() + " should implement RequestWithFileId");
        }
    }

    @Test
    @DisplayName("Should test thread safety of setFileId")
    void testThreadSafety() throws InterruptedException {
        // Given
        RequestWithFileId request = new Smb2CloseRequest(mockConfig, emptyFileId);
        int threadCount = 10;

        byte[] fileNameBytes = fileName.getBytes(StandardCharsets.UTF_16LE);
        int totalSize = 12 + fileNameBytes.length + 50; // Extra space for safety
        byte[] buffer = new byte[totalSize];

        // Write next entry offset (4 bytes)
        SMBUtil.writeInt4(nextOffset, buffer, 0);

        // Write action (4 bytes)

        assertNull(emptyOptional.orElse(null));
    }

    @Test
    public void test_ofNullable_multipleTypesInSequence() {
        // Test multiple different types in sequence to ensure type safety
        OptionalEntity<String> stringOpt = OptionalUtil.ofNullable("string");
        OptionalEntity<Integer> intOpt = OptionalUtil.ofNullable(42);
        OptionalEntity<Boolean> boolOpt = OptionalUtil.ofNullable(true);

    }

    @Test
    @DisplayName("Test concurrent access")
    void testConcurrentAccess() throws InterruptedException {
        // Test thread safety - multiple threads accessing the same response
        final int THREAD_COUNT = 10;
        Thread[] threads = new Thread[THREAD_COUNT];
        final boolean[] success = new boolean[THREAD_COUNT];

     * Each evaluation creates a new Script instance to ensure thread-safe binding isolation.
     * The DI container is automatically injected into the binding map as "container".</p>
     *
     * @param template the Groovy script to evaluate (null-safe, returns null if empty)
     * @param paramMap the parameters to bind to the script (null-safe, treated as empty map if null)

    try {
      /*
       * UnsafeByteArray uses Unsafe.getLong() in an unsupported way, which is known to cause
       * crashes on Android when running in 32-bit mode. For maximum safety, we shouldn't use
       * Unsafe.getLong() at all, but the performance benefit on x86_64 is too great to ignore, so
       * as a compromise, we enable the optimization only on platforms that we specifically know to

     */
    long deadline = System.nanoTime() + unit.toNanos(timeout);
    int added = 0;
    while (added < numElements) {
      // we could rely solely on #poll, but #drainTo might be more efficient when there are multiple
      // elements already available (e.g. LinkedBlockingQueue#drainTo locks only once)
      added += q.drainTo(buffer, numElements - added);