* whether nulls were to be permitted or forbidden, but presumably the eventual fix will be to
   * permit them, as it seems more likely that code would depend on that behavior than on the other.
   * Thus, we say the bug is in add(), which fails to support null.
   */
  @J2ktIncompatible
  @GwtIncompatible // reflection
  public static Method getAddNullSupportedMethod() {

///

It will:

* Return that status code in the response.
* Document it as such in the OpenAPI schema (and so, in the user interfaces):

<img src="/img/tutorial/response-status-code/image01.png">

/// note

Some response codes (see the next section) indicate that the response does not have a body.

FastAPI knows this, and will produce OpenAPI docs that state there is no response body.

///

            "Indicates a Windows NT Server could not be contacted or that objects within the domain are protected such that necessary information could not be retrieved.",
            "The specified domain did not exist.", "The directory name is invalid.", "Access is denied.",

            }

            // Check that sessionId was generated
            assertNotNull(options.sessionId);
            assertTrue(options.sessionId.matches("\\d{14}"));
        } catch (Exception e) {
            // Expected since we're not setting up the full container
        }
    }

    public void test_process_withCustomSessionId() throws Exception {
        // Test that custom sessionId is sanitized

   * ValueGraphBuilder}.
   *
   * <p>The returned builder can be used for populating an {@link ImmutableValueGraph}.
   *
   * <p>Note that the returned builder will always have {@link #incidentEdgeOrder} set to {@link
   * ElementOrder#stable()}, regardless of the value that was set in this builder.
   *
   * @since 28.0
   */
  public <N1 extends N, V1 extends V> ImmutableValueGraph.Builder<N1, V1> immutable() {

            <goals>
              <goal>manifest</goal>
            </goals>
          </execution>
        </executions>
        <configuration>
          <instructions>
            <!-- Silence a warning that claims that META-INF/versions/9/... is the "wrong directory" for our classes. -->
            <_fixupmessages>^Classes found in the wrong directory: .*</_fixupmessages>
            <Export-Package>

   * even to an intermediate buffer) should be considerably more efficient than potentially
   * copying the CharSequence to a String and then calling getBytes(Charset) on that String, in
   * reality there are optimizations that make the getBytes(Charset) approach considerably faster,
   * at least for commonly used charsets like UTF-8.
   */

  @Override
  @CanIgnoreReturnValue

        // For coverage, we'll ensure the method doesn't throw MalformedURLException for a valid URL
        // and that it attempts to create an SmbFile.
        // We cannot directly mock `new SmbFile()`, so we rely on the fact that if it doesn't throw, it's working as expected.

        // This test primarily ensures that the wrapper correctly handles the MalformedURLException
        // and delegates the SmbFile creation.

        }
    }

    @Test
    void testWriteSetupWireFormat() {
        // Test that writeSetupWireFormat returns 0
        byte[] dst = new byte[100];
        int result = response.writeSetupWireFormat(dst, 10);
        assertEquals(0, result);
    }

    @Test
    void testWriteParametersWireFormat() {
        // Test that writeParametersWireFormat returns 0
        byte[] dst = new byte[100];

	defer logger.AuditLog(ctx, w, r, claims)

	// Check auth here (otherwise r.Form will have unexpected values from
	// the call to `parseForm` below), but return failure only after we are
	// able to validate that it is a valid STS request, so that we are able
	// to send an appropriate audit log.
	user, apiErrCode := checkAssumeRoleAuth(ctx, r)

	if err := parseForm(r); err != nil {
		writeSTSErrorResponse(ctx, w, ErrSTSInvalidParameterValue, err)