// toString() uses lastWriteTime directly without offset
        assertTrue(resp.toString().contains(new Date(1630000000000L).toString()));
    }

    // Buffer helpers to build SMB basic file info wire format.
    // SMB uses little-endian byte order
    private static void writeLong(byte[] buf, int offset, long val) {
        for (int i = 0; i < 8; i++) {
            buf[offset + i] = (byte) ((val >>> (8 * i)) & 0xFF);

  private val bytesIn = Buffer()
  private val hpackReader = Hpack.Reader(bytesIn, 4096)

  protected fun testDecoder(story: Story) {
    for (testCase in story.cases) {
      val encoded = testCase.wire ?: continue
      bytesIn.write(encoded)
      hpackReader.readHeaders()
      assertSetEquals(
        "seqno=$testCase.seqno",
        testCase.headersList,
        hpackReader.getAndResetHeaderList(),
      )

        // Only compare the first 6 bytes that were actually written
        byte[] actualWritten = new byte[6];
        System.arraycopy(buffer, 0, actualWritten, 0, 6);
        assertArrayEquals(expected, actualWritten, "wire format should match expectation");
    }

    static Stream<Arguments> validParams() {
        // fid 0x1234, lastWriteTime 0 -> UTime all 0xFF

### Technische Details: `root_path`

Wenn Sie eine Unteranwendung wie oben beschrieben mounten, kümmert sich FastAPI darum, den Mount-Pfad für die Unteranwendung zu kommunizieren, mithilfe eines Mechanismus aus der ASGI-Spezifikation namens `root_path`.

Auf diese Weise weiß die Unteranwendung, dass sie dieses Pfadpräfix für die Benutzeroberfläche der Dokumentation verwenden soll.

... und dann zeigt die Swagger-Oberfläche die Syntaxhervorhebung nicht mehr an:

<img src="/img/tutorial/extending-openapi/image03.png">

## Das Theme ändern

Auf die gleiche Weise könnten Sie das Theme der Syntaxhervorhebung mit dem Schlüssel `syntaxHighlight.theme` festlegen (beachten Sie, dass er einen Punkt in der Mitte hat):

{* ../../docs_src/configure_swagger_ui/tutorial002.py hl[3] *}

        final int start = bufferIndex;
        if (in.read(buffer, bufferIndex, length) != length) {
            throw new IOException("invalid session request wire format");
        }
        bufferIndex += calledName.readWireFormat(buffer, bufferIndex);
        bufferIndex += callingName.readWireFormat(buffer, bufferIndex);
        return bufferIndex - start;
    }

 * referenced in the project's POM file. This allows for greater flexibility
 * and control over the build environment, enabling developers to specify
 * the exact versions of tools they wish to use.</p>
 *
 * <p>
 * Toolchains can be obtained through the {@link org.apache.maven.api.services.ToolchainManager ToolchainManager}
 * service. This service provides methods to retrieve and manage toolchains defined

        }
        return buffer[bufferIndex] & 0xFF;
    }

    int type, length;

    /**
     * Writes the packet to the specified byte array in wire format.
     *
     * @param dst the destination byte array to write to
     * @param dstIndex the starting index in the destination array
     * @return written bytes
     */

        byte[] copiedFileId = new byte[16];
        System.arraycopy(buffer, 8, copiedFileId, 0, 16);
        assertArrayEquals(expectedFileId, copiedFileId);
    }

    @Test
    @DisplayName("Test wire format structure matches SMB2 specification")
    void testWireFormatStructure() {
        byte[] buffer = new byte[256];
        Arrays.fill(buffer, (byte) 0xCC); // Fill with pattern to detect unwritten areas

    this.errorMessage = errorMessage;
  }

  // Override hashCode() to access delegate directly (so that it doesn't trigger the validate() call
  // via delegate()); it seems inappropriate to throw ISE on this method.
  @Override
  public int hashCode() {
    return delegate.hashCode();
  }

  private void validate() {
    // Don't use checkState(), because we don't want the overhead of generating the error message