initCollectionWithNullElement();
    try {
      assertSetCount(null, 1);
    } catch (UnsupportedOperationException tolerated) {
    }
  }

  // Negative count.

  @CollectionFeature.Require(SUPPORTS_REMOVE)
  public void testSetCount_negative_removeSupported() {
    assertThrows(IllegalArgumentException.class, () -> setCountNoCheckReturnValue(e3(), -1));
  }

    public void setExistNextPage(final boolean existNextPage) {
        this.existNextPage = existNextPage;
    }

    /**
     * Gets the number of items per page.
     * If the page size is not set or is zero or negative, returns the default page size.
     *
     * @return the number of items per page
     */
    public int getPageSize() {
        if (pageSize <= 0) {
            pageSize = getDefaultPageSize();
        }

     *
     * @return The full URL of the artifact, never {@code null}.
     */
    String getUrl();

    /**
     * The size of the artifact in bytes.
     *
     * @return The of the artifact in bytes or a negative value if unknown.
     */
    long getContentLength();

    /**
     * Gets the timestamp when the transfer of this artifact was started.
     *

        assertEquals(Integer.MAX_VALUE, negotiationResponse.getReceiveBufferSize());
        assertEquals(Integer.MAX_VALUE, negotiationResponse.getTransactionBufferSize());

        // Test negative values (though not typical, should be tested)
        when(negotiationResponse.getSendBufferSize()).thenReturn(-1);
        when(negotiationResponse.getReceiveBufferSize()).thenReturn(-1);

        @Test
        @DisplayName("Should handle negative offset in verify method")
        void testVerifyNegativeOffset() {
            byte[] data = new byte[128];
            boolean result = digest.verify(data, -1, 100, 0, response);
            assertFalse(result, "Should return false for negative offset");
        }

        @Test
        @DisplayName("Should handle negative length in verify method")

  @Override
  public final int add(@ParametricNullness E element, int occurrences) {
    if (occurrences == 0) {
      return count(element);
    }
    checkArgument(occurrences > 0, "occurrences cannot be negative: %s", occurrences);
    int entryIndex = backingMap.indexOf(element);
    if (entryIndex == -1) {
      backingMap.put(element, occurrences);
      size += occurrences;
      return 0;
    }

        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 approach might be
        more appropriate.

      default:
        throw new AssertionError();
    }
    return increment ? div + signum : div;
  }

  /**
   * Returns {@code x mod m}, a non-negative value less than {@code m}. This differs from {@code x %
   * m}, which might be negative.
   *
   * <p>For example:
   *
   * {@snippet :
   * mod(7, 4) == 3
   * mod(-7, 4) == 1
   * mod(-1, 4) == 3
   * mod(-8, 4) == 0
   * mod(8, 4) == 0

### `response_model` ou Tipo de Retorno { #response-model-or-return-type }

Neste caso, como os dois modelos são diferentes, se anotássemos o tipo de retorno da função como `UserOut`, o editor e as ferramentas reclamariam que estamos retornando um tipo inválido, pois são classes diferentes.

É por isso que neste exemplo temos que declará-lo no parâmetro `response_model`.

        assertEquals(1, config.getChannelBindingPolicy());
    }

    @Test
    void testEdgeCaseValues() throws CIFSException {
        Properties props = new Properties();

        // Test zero and negative values
        props.setProperty("jcifs.smb.client.maxChannels", "0");
        PropertyConfiguration config = new PropertyConfiguration(props);
        assertEquals(4, config.getMaxChannels()); // Should use default when 0