The recommended way to handle the *startup* and *shutdown* is using the `lifespan` parameter of the `FastAPI` app as described above. If you provide a `lifespan` parameter, `startup` and `shutdown` event handlers will no longer be called. It's all `lifespan` or all events, not both.

    You can probably skip this part.

There's an alternative way to define this logic to be executed during *startup* and during *shutdown*.

  <version>0.1</version>
  <packaging>jar</packaging>

  <name>Maven Integration Test :: MNG-4208</name>
  <description>
    Test that CLI properties specified by the user override project properties during interpolation.
  </description>

  <properties>
    <testProperty>FAILED</testProperty>
    <interpolatedProperty>${testProperty}</interpolatedProperty>
  </properties>

    <version>0.1</version>
  </parent>

  <artifactId>child</artifactId>

  <name>Maven Integration Test :: MNG-3899</name>
  <description>
    Test that build extensions are properly merged during inheritance.
  </description>

  <build>
    <!-- project extensions should precede inherited extensions -->
    <extensions>
      <extension>
        <groupId>org.apache.maven.its.mng3899</groupId>

  @Override
  public final void tearDown() {
    try {
      sloppyTearDown();
    } catch (Throwable t) {
      logger.log(Level.INFO, "exception thrown during tearDown: " + t.getMessage(), t);
    }
  }

  public abstract void sloppyTearDown() throws Exception;

        return source != null ? source.getLocation() : "";
    }

    @Override
    public String toString() {
        return String.valueOf(model);
    }

package replication

import (
	"fmt"
)

// Error is the generic type for any error happening during tag
// parsing.
type Error struct {
	err error
}

// Errorf - formats according to a format specifier and returns
// the string as a value that satisfies error of type tagging.Error
func Errorf(format string, a ...interface{}) error {
	return Error{err: fmt.Errorf(format, a...)}
}

// Unwrap the internal error.

    <artifactId>parent</artifactId>
    <version>0.1</version>
  </parent>

  <artifactId>child</artifactId>

  <name>Maven Integration Test :: MNG-3979</name>
  <description>
    Test that during inheritance the merging/joining of subtrees with equal identifier doesn't crash if the parent
    POM has a non-empty element and the child POM has an empty element to join.
  </description>

  <properties/>

    private long sessionId;

    private SMBSigningDigest digest;

    private final String targetDomain;
    private final String targetHost;

    private byte[] preauthIntegrityHash;


    SmbSessionImpl ( CIFSContext tf, String targetHost, String targetDomain, SmbTransportImpl transport ) {
        this.transportContext = tf;
        this.targetDomain = targetDomain;

	// Service:*:istio-pilot - compare Services called "istio-pilot" in all namespaces.
	selectResources string
	// ignoreResources ignores all listed items during comparison. It uses the same list format as selectResources.
	ignoreResources string
	// renameResources identifies renamed resources before comparison.
	// The format of each renaming pair is A->B, all renaming pairs are comma separated.

 * What should be done with the incoming socket.
 *
 * Be careful when using values like [DisconnectAtEnd], [ShutdownInputAtEnd]
 * and [ShutdownOutputAtEnd] that close a socket after a response, and where there are
 * follow-up requests. The client is unblocked and free to continue as soon as it has received the
 * entire response body. If and when the client makes a subsequent request using a pooled socket the