Assertions.assertEquals(lastAccess, info.getLastAccessTime());
        Assertions.assertEquals(size, info.getSize());
    }

    // Supplies a range of normal and edge case values.
    private static Stream<Arguments> valueProvider() {
        return Stream.of(Arguments.of(0, 0L, 0L, 0L, 0L), // all zeros
                Arguments.of(1, 1L, 1L, 1L, 1L), // ones

        verifyNoMoreInteractions(smbFile);
    }

    @ParameterizedTest(name = "getName='{0}' -> accepted={1}")
    @MethodSource("nameCases")
    @DisplayName("accept: name-based filter handles normal, empty, and null names")
    void accept_nameBasedFilter_handlesEdgeNames(String name, boolean expected) throws Exception {
        // Arrange: filter that accepts non-empty names ending with .txt

		return ""
	}
	return p.roleArn.String()
}

// UserInfo returns claims for authenticated user from userInfo endpoint.
//
// Some OIDC implementations such as GitLab do not support
// claims as part of the normal oauth2 flow, instead rely
// on service providers making calls to IDP to fetch additional
// claims available from the UserInfo endpoint

   * @throws NullPointerException if {@code element} is null and this implementation does not permit
   *     null elements. Note that if {@code occurrences} is zero, the implementation may opt to
   *     return normally.
   */
  @CanIgnoreReturnValue
  int add(@ParametricNullness E element, int occurrences);

  /**
   * Adds a single occurrence of the specified element to this multiset.
   *

 * bound. However, it would also let them create `new TypeParameter<@Nullable T>() {}`, which
 * wouldn't behave as users might expect. Additionally, it's not clear how the TypeToken API could
 * support even a "normal" `TypeParameter<T>` when `<T>` has a nullable bound. (See the discussion
 * on TypeToken.where.) So, in the interest of failing fast and encouraging the user to switch to a

     *
     * @throws Exception
     */
    @Test
    public void testReadBytes_NormalFile() throws Exception {
        final File normalFile = tempFolder.newFile("normal.txt");
        final String content = "Test content for normal file";

        try (FileOutputStream fos = new FileOutputStream(normalFile)) {
            fos.write(content.getBytes("UTF-8"));
        }

The API docs use **Swagger UI** and **ReDoc**, and each of those need some JavaScript and CSS files.

By default, those files are served from a <abbr title="Content Delivery Network: A service, normally composed of several servers, that provides static files, like JavaScript and CSS. It's commonly used to serve those files from the server closer to the client, improving performance.">CDN</abbr>.

{* ../../docs_src/handling_errors/tutorial001_py310.py hl[1] *}

### Lever une `HTTPException` dans votre code { #raise-an-httpexception-in-your-code }

`HTTPException` est une exception Python normale avec des données supplémentaires pertinentes pour les API.

Comme il s'agit d'une exception Python, vous ne la `return` pas, vous la `raise`.

   *
   * Additionally, it seems that nestmates do not help with runtime reflection under *Android*, even
   * when we use a newer -source and -target. That doesn't normally matter for AbstractFutureState,
   * since Android should normally succed in using UnsafeAtomicHelper and thus never even try the
   * problematic AtomicReferenceFieldUpdaterAtomicHelper code path. However, the same problem *does*

  }

  /**
   * Configure the server to [want client auth][SSLSocket.setWantClientAuth]. If the
   * client presents a certificate that is [trusted][TrustManager] the handshake will
   * proceed normally. The connection will also proceed normally if the client presents no
   * certificate at all! But if the client presents an untrusted certificate the handshake
   * will fail and no connection will be established.
   */