* </p>
 *
 * <p>
 * It handles potential exceptions during file creation and storage, throwing
 * {@link org.codelibs.fess.crawler.exception.CrawlerSystemException} in case of errors.
 * </p>
 *
 * <p>
 * The {@link #storeData(ResponseData, ResultData)} method is the main entry point for storing
 * the content of a crawled resource. The {@link #getData(AccessResultData)} method retrieves

        // Then - should still read 4 bytes regardless of reserved field value
        assertEquals(4, bytesRead);
    }

    @Test
    @DisplayName("Should handle edge case structure sizes")
    void testEdgeCaseStructureSizes() {
        // Test minimum invalid size (0)
        byte[] buffer = new byte[256];
        SMBUtil.writeInt2(0, buffer, 0);

 * methods of the delegate. For example, overriding {@link #put} alone <i>will not</i> change the
 * behavior of {@link #putAll}, which can lead to unexpected behavior. In this case, you should
 * override {@code putAll} as well, either providing your own implementation, or delegating to the
 * provided {@code standardPutAll} method.
 *

     * StackOverflowError: We can't reliably call setException(error).
     *
     * - Any kind of Error from a listener. Even if we could distinguish that case (by exposing some
     * extra state from AbstractFuture), our options are limited: A call to setException() would be
     * a no-op. We could log, but if that's what we really want, we should modify

            int result = upgradeGoal.testExecuteWithTargetModel(context, "4.0.0");

            // The exact behavior depends on implementation, but it should handle gracefully
            // and not crash the entire upgrade process
            assertTrue(result >= 0, "Should handle .mvn creation failure gracefully");
        }
    }

    /**
     * Testable subclass that exposes protected methods for testing.

## Anwendungsfall { #use-case }

Beginnen wir mit einem Beispiel-**Anwendungsfall** und schauen uns dann an, wie wir ihn mit dieser Methode implementieren können.

{* ../../docs_src/body/tutorial001_py310.py hl[5:9] *}

Assim como quando declaramos parâmetros de consulta, quando um atributo do modelo possui um valor padrão, ele se torna opcional. Caso contrário, se torna obrigatório. Use `None` para torná-lo opcional.

Por exemplo, o modelo acima declara um JSON "`object`" (ou `dict` no Python) como esse:

```JSON
{
    "name": "Foo",

    For example, in an HTTP Bearer token scheme, the client will send a header
    like:

    ```
    Authorization: Bearer deadbeef12346
    ```

    In this case:

    * `scheme` will have the value `"Bearer"`
    * `credentials` will have the value `"deadbeef12346"`
    """

    scheme: Annotated[
        str,
        Doc(
            """

                    dots++;
                    i++;
                }
            }
        } else {
            switch (hostName.hexCode) {
            case 0x1B:
            case 0x1C:
            case 0x1D:
                calledName = SMBSERVER_NAME;
            }
        }

        return calledName;
    }

    /**

apiserver to same-host redirects.  If nodes are configured to respond to CRI streaming requests on a different host interface than what the apiserver makes requests on (only the case if not using the built-in dockershim & setting the kubelet flag `--redirect-container-streaming=true`), then these requests will be broken. In that case, the feature can be temporarily disabled until the node configuration is corrected. We suggest setting `--redirect-container-streaming=false` on the kubelet to avoid issue...