Here's what to keep in mind and how to review a pull request:

### Understand the problem { #understand-the-problem }

* First, make sure you **understand the problem** that the pull request is trying to solve. It might have a longer discussion in a GitHub Discussion or issue.

* There's also a good chance that the pull request is not actually needed because the problem can be solved in a **different way**. Then you can suggest or ask about that.

     */
    @Nonnull
    List<Profile> getActiveExternalProfiles();

    /**
     * Gets the problem collector that collected problems encountered during the project building.
     *
     * @return the problem collector that collected problems encountered during the project building
     */
    @Nonnull
    ProblemCollector<ModelProblem> getProblemCollector();

    /**

          <offlineLinks>
            <!-- We need local copies of some of these for 2 reasons: a User-Agent problem (https://stackoverflow.com/a/47891403/28465) and an SSL problem (https://issues.apache.org/jira/browse/MJAVADOC-507). If we choose to work around the User-Agent problem, we can go back to <links>, sidestepping the SSL problem. -->
            <offlineLink>

    }

    @Test
    public void test_multiLevelCause() {
        // Test with nested exceptions
        Throwable rootCause = new IllegalStateException("Root problem");
        Throwable intermediateCause = new RuntimeException("Intermediate problem", rootCause);
        GsaConfigException exception = new GsaConfigException("Top level GSA error", intermediateCause);

        assertNotNull(exception);

          <offlineLinks>
            <!-- We need local copies of some of these for 2 reasons: a User-Agent problem (https://stackoverflow.com/a/47891403/28465) and an SSL problem (https://issues.apache.org/jira/browse/MJAVADOC-507). If we choose to work around the User-Agent problem, we can go back to <links>, sidestepping the SSL problem. -->
            <offlineLink>

  }

  private static class StringWrapper {
    private final String value;

    StringWrapper(String value) {
      this.value = value;
    }
  }

  @GwtIncompatible // J2CL generics problem
  public void testAndThen() {
    Converter<StringWrapper, String> first =
        new Converter<StringWrapper, String>() {
          @Override
          protected String doForward(StringWrapper object) {

      // null?  no problem
    }

    public static void staticOneArgJsr305NullableCorrectlyDoesNotThrowNpe(
        @javax.annotation.Nullable String s) {
      // null?  no problem
    }

    public static void staticOneArgNullableCorrectlyDoesNotThrowNpe(@Nullable String s) {
      // null?  no problem
    }

So, you can declare your function as:

{* ../../docs_src/path_params_numeric_validations/tutorial002_py310.py hl[7] *}

But keep in mind that if you use `Annotated`, you won't have this problem, it won't matter as you're not using the function parameter default values for `Query()` or `Path()`.

{* ../../docs_src/path_params_numeric_validations/tutorial002_an_py310.py *}

      e is FileNotFoundException
  }

  private fun isRecoverable(
    e: IOException,
    requestSendStarted: Boolean,
  ): Boolean {
    // If there was a protocol problem, don't recover.
    if (e is ProtocolException) {
      return false
    }

    // If there was an interruption don't recover, but if there was a timeout connecting to a route

## Decision

Introduce a "UI" architecture module to the core platform, and move the user interaction services to this new module.

This includes:

- Logging and progress services.
- Problem generation services (aka the "problems API").
- User prompting services.
- Build options infrastructure.
- The console and CLI, as a specific implementation of these services.