@Override
    public void setRootLoggerLevel(Level level) {
        LOGGER.warn("setRootLoggerLevel: operation not supported");
    }

    @Override
    public void activate() {
        LOGGER.warn("activate(): operation not supported");
    }

Before FastAPI 0.106.0, raising exceptions after `yield` was not possible, the exit code in dependencies with `yield` was executed *after* the response was sent, so [Exception Handlers](../tutorial/handling-errors.md#install-custom-exception-handlers){.internal-link target=_blank} would have already run.

 * @param request The original request that was processed
 * @param result The result of the request, if successful; may be null if an error occurred
 * @param error Any error that occurred during processing; null if the request was successful
 * @since 4.0.0
 */
@Experimental
public record RequestResult<REQ extends Request<?>, REP extends Result<REQ>>(
        /**
         * The original request that was processed
         */
        REQ request,

	},
	ErrSTSMalformedPolicyDocument: {
		Code:           "MalformedPolicyDocument",
		Description:    "The request was rejected because the policy document was malformed.",
		HTTPStatusCode: http.StatusBadRequest,
	},
	ErrSTSInsecureConnection: {
		Code:           "InsecureConnection",
		Description:    "The request was made over a plain HTTP connection. A TLS connection is required.",
		HTTPStatusCode: http.StatusBadRequest,
	},

     */
    String getArtifactId();

    /**
     * The repository from which the plugin prefix was resolved.
     *
     * @return The repository from which the plugin prefix was resolved or {@code null} if the prefix was resolved from
     *         the supplied POM.
     */
    ArtifactRepository getRepository();

_2014-03-29_

 * Fix bug where the Content-Length header was not always dropped when
   following a redirect from a POST to a GET.
 * Implement basic support for `Thread.interrupt()`. OkHttp now checks
   for an interruption before doing a blocking call. If it is interrupted,
   it throws an `InterruptedIOException`.

## Version 1.5.2

_2014-03-17_

 * Fix bug where deleting a file that was absent from the `HttpResponseCache`

            LOGGER.warn("");
            LOGGER.warn("Some problems were encountered while building the effective settings");

            for (SettingsProblem problem : settingsResult.getProblems()) {
                LOGGER.warn("{} @ {}", problem.getMessage(), problem.getLocation());
            }
            LOGGER.warn("");
        }
    }

        requireNonNull(level, "level");
        requireNonNull(message, "message");
        switch (level) {
            case ERROR -> logger.error(message, error);
            case WARN -> logger.warn(message, error);
            case INFO -> logger.info(message, error);
            case DEBUG -> logger.debug(message, error);
            default -> logger.error("UNKNOWN LEVEL {}: {}", level, message, error);
        }

            // Do NOT call setRootLoggerLevel - this is the fix!
        }

        // Verify that setRootLoggerLevel was not called
        assertEquals(0, slf4jConfiguration.setRootLoggerLevelCallCount);

        // Verify that system property was not set
        assertNull(System.getProperty(Constants.MAVEN_LOGGER_DEFAULT_LOG_LEVEL));
    }

    @Test
    void testVerboseOptionSetsSystemProperty() {

  The scheduling hints allowed the scheduler to retry scheduling a Pod that was previously rejected by the VolumeBinding plugin only if a new resource referenced by the plugin was created or an existing resource referenced by the plugin was updated. ([#124961](https://github.com/kubernetes/kubernetes/pull/124961), [@bells17](https://github.com/bells17)) [SIG Scheduling and Storage]