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

                    - 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

### Existing properties in existing classes

This is out of scope for this ADR.  Migrating an existing property to lazy types is being handled in a different way.

### Conventions

Once a new property has been introduced, you need to consider what its conventions will be.

     * It will parse valid directives and ignore invalid ones, ensuring that partial
     * content can be extracted even from poorly formatted files.</p>
     *
     * <p>The following errors are handled gracefully (line is skipped, parsing continues):</p>
     * <ul>
     * <li>Invalid directive formats</li>
     * <li>Unknown directives</li>
     * <li>Invalid crawl-delay values (non-numeric, negative)</li>

        URL url = new URL("storage://mybucket/path/file%20with%20spaces.txt");
        Handler handler = new Handler();
        URLConnection conn = handler.openConnection(url);

        Handler.StorageURLConnection storageConn = (Handler.StorageURLConnection) conn;

        assertEquals("mybucket", getField(storageConn, "bucketName"));
        // URL decoding is handled by URL class

participant client as Client
participant handler as Exception handler
participant dep as Dep with yield
participant operation as Path Operation
participant tasks as Background tasks

    Note over client,operation: Can raise exceptions, including HTTPException
    client ->> dep: Start request
    Note over dep: Run code up to yield
    opt raise Exception
        dep -->> handler: Raise Exception

    }

    /*MNG-11062*/
    @Test
    void testTargetPathEdgeCases() {
        // Test null targetPath (should be handled gracefully)
        Resource nullTargetResource = new Resource();
        nullTargetResource.setDirectory("src/test/null-target");
        // targetPath is null by default

 * 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 {

    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() {

        @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() {