// Verify all values are set correctly
        assertEquals(TEST_CREATE_TIME, info.getCreateTime());
        assertEquals(TEST_LAST_ACCESS_TIME, info.getLastAccessTime());
        assertEquals(TEST_LAST_WRITE_TIME, info.getLastWriteTime());
        assertEquals(TEST_ATTRIBUTES, info.getAttributes());
    }

    @Test
    @DisplayName("Test getFileInformationLevel returns correct value")
    void testGetFileInformationLevel() {

                return process.exitValue();
            } catch (final Exception e) {
                logger.error("Could not destroy a process correctly.", e);
            }
        }
        return -1;
    }

    /**
     * Gets the set of session IDs for all currently running processes.
     *
     * @return set of session IDs for running processes
     */
    public Set<String> getRunningSessionIdSet() {

    @BeforeEach
    void setUp() {
        msrpcShareEnum = new MsrpcShareEnum(TEST_SERVER_NAME);
    }

    @Test
    void testConstructor() {
        // Test that the constructor initializes the object correctly
        MsrpcShareEnum shareEnum = new MsrpcShareEnum(TEST_SERVER_NAME);
        assertNotNull(shareEnum);

        // Verify the server name is properly formatted with double backslashes
        try {

Create a function to be run as the background task.

It is just a standard function that can receive parameters.

It can be an `async def` or normal `def` function, **FastAPI** will know how to handle it correctly.

In this case, the task function will write to a file (simulating sending an email).

And as the write operation doesn't use `async` and `await`, we define the function with normal `def`:

X25519MLKEM768 by default. The default can be reverted using the
[`tlsmlkem` setting](/pkg/crypto/tls/#Config.CurvePreferences).
This can be useful when dealing with buggy TLS servers that do not handle large records correctly,
causing a timeout during the handshake (see [TLS post-quantum TL;DR fail](https://tldr.fail/)).
Go 1.24 also removed X25519Kyber768Draft00 and the Go 1.23 `tlskyber` setting.

type Buffer struct {
	buf      []byte // contents are the bytes buf[off : len(buf)]
	off      int    // read at &buf[off], write at &buf[len(buf)]
	lastRead readOp // last read operation, so that Unread* can work correctly.

	// Copying and modifying a non-zero Buffer is prone to error,
	// but we cannot employ the noCopy trick used by WaitGroup and Mutex,
	// which causes vet's copylocks checker to report misuse, as vet

 * result in the chain, or will be zero if every comparison result was zero.
 *
 * <p><b>Note:</b> {@code ComparisonChain} instances are <b>immutable</b>. For this utility to work
 * correctly, calls must be chained as illustrated above.
 *
 * <p>Performance note: Even though the {@code ComparisonChain} caller always invokes its {@code

        // Verify results
        assertEquals(20, bytesRead);
        assertEquals(fileAttributes, response.getAttributes());
        assertEquals(fileSize, response.getSize());

        // Verify time was read correctly (accounting for UTime conversion)
        long readTime = (Long) getFieldValue(response, "lastWriteTime");
        // UTime is seconds since 1970, so we need to compare at second precision

        assertNotNull(packet);
        assertEquals(SessionServicePacket.SESSION_REQUEST, packet.type);
    }

    @Test
    @DisplayName("writeTrailerWireFormat should write both names correctly")
    void testWriteTrailerWireFormat() {
        when(mockCalledName.getName()).thenReturn("SERVER");
        when(mockCalledName.getNameType()).thenReturn(0x20);
        when(mockCalledName.getScope()).thenReturn(null);

         * repository's layout to allow pointing at artifacts within the repository. Unfortunately,
         * DefaultRepositoryLayout does not correctly describe the layout of a local repository which unlike a remote
         * repository never uses timestamps in the filename of a snapshot artifact. The discrepancy gets notable when a