```console
$ <font color="#4E9A06">fastapi</font> dev <u style="text-decoration-style:single">main.py</u>
<font color="#3465A4">INFO    </font> Using path <font color="#3465A4">main.py</font>
<font color="#3465A4">INFO    </font> Resolved absolute path <font color="#75507B">/home/user/code/awesomeapp/</font><font color="#AD7FA8">main.py</font>

          throw new UnsupportedOperationException(
              "Annotation methods are not supported on synthetic TypeVariables created during type"
                  + " resolution. The semantics of annotations on resolved types with modified"
                  + " bounds are undefined. Use the original TypeVariable for annotation access."
                  + " See b/147144588.");
        }

                // groupId, artifactId, version and classifier coordinates. This is in consequence
                // a self reference or in other words a circular reference which can not being resolved.
                addViolation(
                        problems,
                        Severity.FATAL,
                        Version.V31,
                        prefix + "[" + key + "]",

 * located in).
 * - share + uncpath within it: This is the relevant information for most SMB requests. Both are adjusted by DFS
 * referrals. Nested resources will inherit the information already resolved by the parent resource.
 *
 * Invariant:
 * A directory resource must have a trailing slash/backslash for both URL and UNC path at all times.
 *
 * @author mbechler
 *
 */

            DfsReferralData dr = this.ctx.getDfs().resolve(this.ctx, loc.getServer(), loc.getShare(), loc.getUNCPath());
            if (dr != null) {
                if (log.isDebugEnabled()) {
                    log.debug("Resolved " + rfullpath + " -> " + dr);
                }

                final String dunc = loc.handleDFSReferral(dr, rpath);
                if (request != null) {
                    request.setPath(dunc);

          throw new UnsupportedOperationException(
              "Annotation methods are not supported on synthetic TypeVariables created during type"
                  + " resolution. The semantics of annotations on resolved types with modified"
                  + " bounds are undefined. Use the original TypeVariable for annotation access."
                  + " See b/147144588.");
        }

        allOptionalSelectors.addAll(projectActivation.getRequiredActiveProjectSelectors());
        // We intentionally ignore the results of this method.
        // As a side effect it will log the optional projects that could not be resolved.
        projectSelector.getOptionalProjectsBySelectors(request, session.getAllProjects(), allOptionalSelectors);
    }

    /**

    /** Specify the required dependencies in a specified scope */
    private String dependencyResolutionRequired = null;

    /**
     * The scope of (transitive) dependencies that should be collected but not resolved.
     * @since 3.0-alpha-3
     */
    private String dependencyCollectionRequired;

    /**  By default, the Mojo needs a Maven project to be executed */
    private boolean projectRequired = true;

If you have a large number of messages of different types, filtering by severity to see only `Error`s can be helpful when processing the report.
Errors are the only type of issues that must be resolved for the `checkBinaryCompatibility` task to succeed.

            log.trace("Using cached attributes (expires in {}ms)", this.attrExpiration - currentTime);
            return this.isExists;
        }

        // Fast path for already resolved existence with recent cache
        if (this.isExists && (currentTime - (this.attrExpiration - getContext().getConfig().getAttributeCacheTimeout())) < 5000) {
            log.trace("Using recent positive existence cache");