opt raise
        dep -->> handler: Raise HTTPException
        handler -->> client: HTTP error response
        dep -->> dep: Raise other exception
    end
    dep ->> operation: Run dependency, e.g. DB session
    opt raise
        operation -->> dep: Raise HTTPException
        dep -->> handler: Auto forward exception
        handler -->> client: HTTP error response

Sometimes there's an action required like calling the application layer or responding to a ping, and the thread discovering the action is not the thread that should do the work. We enqueue a runnable on this executor and it gets handled by one of the executor's threads.

### Locks

We have 3 different things that we synchronize on.

#### Http2Connection

    checkstyleConfig(rootProject.libs.checkStyle) {
      isTransitive = false
    }
  }

  val androidSignature by configurations.creating
  val jvmSignature by configurations.creating

  // Handled in :okhttp directly
  if (project.name != "okhttp") {
    configure<CheckstyleExtension> {
      config = resources.text.fromArchiveEntry(checkstyleConfig, "google_checks.xml")

 * This is typical for Java but atypical for HTTP/2. This is motivated by exception transparency:
 * an [IOException] that was triggered by a certain caller can be caught and handled by that caller.
 */
@Suppress("NAME_SHADOWING")
class Http2Connection internal constructor(
  builder: Builder,
) : Closeable,
  Lockable {

        // Central timezone should match default
        assertEquals(defaultTz, FessUserTimeZoneProcessProvider.centralTimeZone);
    }

    // Test with decimal values in string (should be handled by config)
    public void test_decimalStringValues() {
        FessConfig decimalConfig = new FessConfig.SimpleImpl() {
            private static final long serialVersionUID = 1L;

            @Override

        @Test
        @DisplayName("Should handle null expiration")
        void testNullExpiration() {
            response.setExpiration(null);

            assertNull(response.getExpiration());
        }
    }

    @Nested
    @DisplayName("Async Handling Tests")
    class AsyncHandlingTests {

        @Test
        @DisplayName("Should get and set async handled")
        void testAsyncHandled() {

                    - SmbConstants.MILLISECONDS_BETWEEN_1970_AND_1601;
            assertEquals(expectedTime, readTime);
        }

        // Test zero time separately - it's handled specially
        SMBUtil.writeTime(0L, buffer, 0);
        long readTime = SMBUtil.readTime(buffer, 0);
        // When writing 0, it writes 0 directly, and when reading 0, it returns negative offset

    class EdgeCasesTests {

        @Test
        @DisplayName("Parse handles empty token gracefully")
        void testParseEmptyToken() {
            byte[] emptyToken = new byte[0];
            assertThrows(IOException.class, () -> new NegTokenInit(emptyToken));
        }

        @Test
        @DisplayName("Parse handles null mechanisms array")
        void testNullMechanisms() {

                }
            });
        }

        assertTrue(latch.await(10, TimeUnit.SECONDS), "Concurrent operations should complete");
        executor.shutdown();

        // Circuit breaker should have handled concurrent operations
        assertTrue(successCount.get() > 0, "Should have some successful operations");
        assertTrue(failureCount.get() > 0, "Should have some failed operations");
    }

    @Test

import jcifs.NetbiosName;

/**
 * This class represents a NetBIOS over TCP/IP address. Under normal
 * conditions, users of jCIFS need not be concerned with this class as
 * name resolution and session services are handled internally by the smb package.
 *
 *
 *  * Applications can use the methods <code>getLocalHost</code>,
 * <code>getByName</code>, and
 * <code>getAllByAddress</code> to create a new NbtAddress instance. This