assertThrows(IllegalArgumentException.class, () -> InputValidator.validatePort(65536));
    }

    @Test
    @DisplayName("Test timeout validation")
    void testTimeoutValidation() {
        assertDoesNotThrow(() -> InputValidator.validateTimeout(1000L, "test"));
        assertDoesNotThrow(() -> InputValidator.validateTimeout(0L, "test"));

    variables = {"after": after, "category_id": category_id}
    response = httpx.post(
        github_graphql_url,
        headers=headers,
        timeout=settings.httpx_timeout,
        json={"query": query, "variables": variables, "operationName": "Q"},
    )
    if response.status_code != 200:
        logging.error(

    /**
     * Error categories for SMB operations
     */
    public enum ErrorCategory {
        /** Network-related errors (connection, timeout, etc.) */
        NETWORK,
        /** Authentication and authorization errors */
        AUTHENTICATION,
        /** File system errors (not found, access denied, etc.) */
        FILE_SYSTEM,

        // Assert
        assertNotNull(transPeekNamedPipe);
        assertEquals(TEST_PIPE_NAME, transPeekNamedPipe.name);
        assertEquals(0xFFFFFFFF, transPeekNamedPipe.timeout);
        assertEquals(6, transPeekNamedPipe.maxParameterCount);
        assertEquals(1, transPeekNamedPipe.maxDataCount);
        assertEquals((byte) 0x00, transPeekNamedPipe.maxSetupCount);

         * Only kill local Gradle processes (classpath in checkout directory).
         * Not clean up global Gradle processes (i.e. classpath in ~/.gradle/...).
         * Because the step is not guaranteed to run (e.g. build timeout), we need `KILL_LEAKED_PROCESSES_FROM_PREVIOUS_BUILDS` mode.
         */
        KILL_PROCESSES_STARTED_BY_GRADLE,
        /**

  ```

#### Issue: Large bulk imports timing out

**Solution**:
- Split large files into smaller batches (e.g., 10,000 docs per file)
- Increase timeout in `system.properties`:
  ```properties
  crawler.document.request.timeout=600000
  ```
- Use asynchronous import via Admin UI instead of API

#### Issue: Special characters in documents not displaying correctly

**Solution**:

    }

    @Test
    void testGetServerSid_ConnectionTimeout() throws CIFSException {
        when(sidResolver.getServerSid(any(CIFSContext.class), anyString())).thenThrow(new CIFSException("Connection timeout"));

        assertThrows(CIFSException.class, () -> sidResolver.getServerSid(mockContext, testServerName));
    }

    // Test with large datasets
    @Test

import org.junit.jupiter.api.BeforeEach
import org.junit.jupiter.api.Tag
import org.junit.jupiter.api.Test
import org.junit.jupiter.api.Timeout
import org.junit.jupiter.api.extension.RegisterExtension

@Flaky // STDOUT logging enabled for test
@Timeout(30)
@Tag("Slow")
@Burst
class EventListenerTest(
  val listenerInstalledOn: ListenerInstalledOn = ListenerInstalledOn.Client,
) {
  @RegisterExtension

		t.Fatalf("no error should happen but got %v", err)
	}

	user2 := *GetUser("prepared_stmt2", Config{})
	if err := txCtx.Create(&user2).Error; err == nil {
		t.Fatalf("should failed to create with timeout context")
	}

	if err := tx.Create(&user2).Error; err != nil {
		t.Fatalf("failed to create, got error %v", err)
	}

	var result3 User
	if err := tx.Find(&result3, user2.ID).Error; err != nil {

A single HTTP call may require follow-up requests to be made to handle authentication challenges, redirects, and HTTP-layer timeouts. In such cases multiple connections, requests, and responses may be attempted. Follow-ups are another reason a single call may trigger multiple events of the same type.