Before new features get added to Guava, we really want to be sure that it's for a use case
        that actually comes up in the real world. We want to hear the real-world use case so the
        community can discuss and debate whether this feature is actually the *best* way to address
        the real use case, or whether or not a different abstraction might be more appropriate.

        assertEquals(1, LogStream.level);

        LogStream.setLevel(3);
        assertEquals(3, LogStream.level);

        LogStream.setLevel(10);
        assertEquals(10, LogStream.level);

        // Test negative level
        LogStream.setLevel(-1);
        assertEquals(-1, LogStream.level);
    }

    @Test
    void testGetInstanceWithoutSetInstance() {
        // Test getInstance when no instance has been set

                    });
                    // Sort the array in place by type, then member
                    // Note that Firefox is fine with a sort function returning any positive or negative number, but Chrome 
                    // requires 1 or -1 specifically and ignores higher or lower values.  This sort ought to remain consistent
                    // with the sort used by AbstractAcceptedApiChangesMaintenanceTask.

    class EdgeCaseTests {

        @Test
        @DisplayName("Should handle negative offset")
        void testNegativeOffset() {
            request.setOffset(-1L);
            request.setReadLength(1024);

            byte[] buffer = new byte[256];
            int bytesWritten = request.writeBytesWireFormat(buffer, 0);

            // Negative value should be written as-is (interpreted as unsigned by receiver)

     *     case no change will be made.
     * @return this {@code Builder} object
     * @throws NullPointerException if {@code element} is null
     * @throws IllegalArgumentException if {@code occurrences} is negative, or if this operation
     *     would result in more than {@link Integer#MAX_VALUE} occurrences of the element
     */
    @CanIgnoreReturnValue
    public Builder<E> addCopies(E element, int occurrences) {

                { Long.MAX_VALUE, Long.MAX_VALUE, Long.MAX_VALUE, Long.MAX_VALUE }, // Max values
                { 1L, 2L, 3L, 4L }, // Small values
                { -1L, -2L, -3L, -4L } // Negative values (though unusual for file times)
        };

        for (long[] times : timeValues) {
            // Given
            FileBasicInfo info = new FileBasicInfo(times[0], // create time

            // When & Then
            assertThrows(ArrayIndexOutOfBoundsException.class, () -> response.readBytesWireFormat(buffer, 0));
        }

        @Test
        @DisplayName("Should handle negative structure size as unsigned")
        void testReadBytesWireFormatNegativeAsUnsigned() {
            // Given
            byte[] buffer = new byte[10];
            // Write -1 which will be read as 65535 unsigned

#### O tempo para responder ajuda os invasores { #the-time-to-answer-helps-the-attackers }

Neste ponto, ao perceber que o servidor demorou alguns microssegundos a mais para enviar o retorno "Usuário ou senha incorretos", os invasores irão saber que eles acertaram _alguma coisa_, algumas das letras iniciais estavam certas.

        }

        @Test
        @DisplayName("Should handle negative status codes")
        void testNegativeStatusCode() throws SMBProtocolDecodingException {
            byte[] buffer = new byte[256];
            System.arraycopy(SMBUtil.SMB2_HEADER, 0, buffer, 0, 4);
            SMBUtil.writeInt4(-1, buffer, 8); // negative status

            // Write error response structure at offset 64

        }

        @Test
        @DisplayName("Should handle negative offset")
        void testNegativeOffset() {
            request.setOffset(-1L);
            request.setData(new byte[10], 0, 10);

            byte[] buffer = new byte[256];
            int bytesWritten = request.writeBytesWireFormat(buffer, 0);

            // Negative value should be written as-is (interpreted as unsigned by receiver)