*/

    @Override
    public void write(final byte[] b) throws IOException {
        write(b, 0, b.length);
    }

    /**
     * Tests whether the output stream is currently open.
     *
     * @return true if the stream is open, false otherwise
     */
    public boolean isOpen() {
        return file.isOpen();
    }

    void ensureOpen() throws IOException {

        preauthService.updatePreauthHash(sessionId, "Message2".getBytes());

        byte[] expectedHash = preauthService.getCurrentPreauthHash(sessionId);

        // Validation should pass with correct hash
        assertTrue(preauthService.validatePreauthIntegrity(sessionId, expectedHash));

        // Validation should fail with incorrect hash
        byte[] incorrectHash = new byte[expectedHash.length];

 * code, running tests, packaging the project, and deploying it. Executing a phase
 * triggers all preceding phases, ensuring that each step of the build process is
 * completed in the correct order. The three main lifecycles in Maven are
 * {@link #DEFAULT default}, {@link #CLEAN clean}, and {@link #SITE site}, with the
 * {@code default} lifecycle being the most commonly used for project builds.
 *
 * @since 4.0.0

            // Assert
            verify(signingDigest).sign(largeData, offset, 10, request, response);
        }

        // Verify method was called correct number of times
        verify(signingDigest, times(offsets.length)).sign(any(byte[].class), anyInt(), anyInt(), any(CommonServerMessageBlock.class),
                any(CommonServerMessageBlock.class));
    }

    @Test

     * hashes (meaning negotiated via NTLM HTTP Authentication) and the other does not they will not be equal. This is
     * technically not correct however the server 8 byte challenge would be required to compute and compare the password
     * hashes but that it not available with this method.
     */
    @Override
    public boolean equals(final Object obj) {

        int encodedLength = request.encode(buffer, offset);

        // Verify encoded length
        assertEquals(request.size(), encodedLength);

        // Verify data at correct offset
        assertEquals(DEFAULT_CAPABILITIES, SMBUtil.readInt4(buffer, offset));
        assertEquals(DEFAULT_SECURITY_MODE, SMBUtil.readInt2(buffer, offset + 20));

		} else {
			scanningDisks = append(scanningDisks, disks[i])
			scanningInfos = append(scanningInfos, infos[i])
		}
	}

	// Prefer non-scanning disks over disks which are currently being scanned.
	newDisks = append(newDisks, scanningDisks...)
	newInfos = append(newInfos, scanningInfos...)

	/// Then add healing disks.
	newDisks = append(newDisks, healingDisks...)

...
```

Eso confirma que puedes servir archivos estáticos desde tu aplicación, y que colocaste los archivos estáticos para la documentación en el lugar correcto.

Ahora podemos configurar la aplicación para usar esos archivos estáticos para la documentación.

### Desactiva la documentación automática para archivos estáticos

  # Install the necessary Python, unless it's already present
  pyenv install -s "$TFCI_PYTHON_VERSION"
  pyenv local "$TFCI_PYTHON_VERSION"
  # Do a sanity check to make sure that we using the correct Python version
  python --version
fi

# TFCI Mac VM images do not have twine installed by default so we need to
# install it manually. We use Twine in nightly builds to upload Python packages
# to PyPI.

         * @return the directory file
         */
        public SmbFile getDirectoryFile() {
            return directoryFile;
        }

        /**
         * Checks if directory change monitoring is currently active
         * @return true if watching is active
         */
        public boolean isActive() {
            return active;
        }

        /**
         * Set active status
         *