if (cliRequest.multiModuleProjectDirectory == null) {
            String basedirProperty = System.getProperty(MULTIMODULE_PROJECT_DIRECTORY);
            if (basedirProperty == null) {
                System.err.format("-D%s system property is not set.", MULTIMODULE_PROJECT_DIRECTORY);
                throw new ExitException(1);
            }
            File basedir = new File(basedirProperty);
            try {

Es gibt viele Situationen, in denen Sie einem Client, der Ihre API nutzt, einen Fehler mitteilen müssen.

Dieser Client könnte ein Browser mit einem Frontend sein, ein Code von jemand anderem, ein IoT-Gerät usw.

Sie könnten dem Client mitteilen müssen, dass:

* Der Client nicht genügend Berechtigungen für diese Operation hat.
* Der Client keinen Zugriff auf diese Ressource hat.

Mira p. ej. la sección `### List of English terms and their preferred German translations` en `docs/de/llm-prompt.md`.

        assertEquals("", suggestItem.getText());
    }

    @Test
    public void testMultipleReadingsConversion() {
        // Test conversion of multiple readings to SuggestItem format
        String word = "multi reading";
        float boost = 1.0f;
        List<String> readings = Arrays.asList("reading1", "reading2", "reading3", "reading4", "reading5");

        assertEquals(0, trans2QueryFSInfo.readParametersWireFormat(null, 0, 0));
        assertEquals(0, trans2QueryFSInfo.readDataWireFormat(null, 0, 0));
    }

    @Test
    @DisplayName("Test complete wire format writing")
    void testCompleteWireFormatWriting() {
        trans2QueryFSInfo = new Trans2QueryFSInformation(config, FileSystemInformation.FS_SIZE_INFO);

        byte[] setupBuffer = new byte[256];

        int actualInfoLevel = SMBUtil.readInt2(buffer, 2);
        assertEquals(0x0101, actualInfoLevel); // FILE_BASIC_INFO maps to 0x0101
    }

    @Test
    @DisplayName("Test complete wire format writing")
    void testCompleteWireFormatWriting() {
        when(mockFileInfo.getFileInformationLevel()).thenReturn((byte) FileInformation.FILE_BASIC_INFO);

      replaced with your own identifying information. (Don't include
      the brackets!)  The text should be enclosed in the appropriate
      comment syntax for the file format. We also recommend that a
      file or class name and description of purpose be included on the
      same "printed page" as the copyright notice for easier
      identification within third-party archives.

      replaced with your own identifying information. (Don't include
      the brackets!)  The text should be enclosed in the appropriate
      comment syntax for the file format. We also recommend that a
      file or class name and description of purpose be included on the
      same "printed page" as the copyright notice for easier
      identification within third-party archives.

      replaced with your own identifying information. (Don't include
      the brackets!)  The text should be enclosed in the appropriate
      comment syntax for the file format. We also recommend that a
      file or class name and description of purpose be included on the
      same "printed page" as the copyright notice for easier
      identification within third-party archives.

      replaced with your own identifying information. (Don't include
      the brackets!)  The text should be enclosed in the appropriate
      comment syntax for the file format. We also recommend that a
      file or class name and description of purpose be included on the
      same "printed page" as the copyright notice for easier
      identification within third-party archives.