Первая часть функции, до `yield`, будет выполнена до запуска приложения.

А часть после `yield` будет выполнена после завершения работы приложения.

### Асинхронный менеджер контекста { #async-context-manager }

Если присмотреться, функция декорирована `@asynccontextmanager`.

Это превращает функцию в «асинхронный менеджер контекста».

{* ../../docs_src/events/tutorial003_py310.py hl[1,13] *}

E a parte posterior ao `yield` será executada **depois** de a aplicação ter terminado.

### Gerenciador de contexto assíncrono { #async-context-manager }

Se você verificar, a função está decorada com um `@asynccontextmanager`.

Isso converte a função em algo chamado "**gerenciador de contexto assíncrono**".

{* ../../docs_src/events/tutorial003_py310.py hl[1,13] *}

				suite.TestAccMgmtPlugin(c)
			},
		)
	}
}

// TestAccMgmtPlugin - this test assumes that the access-management-plugin is
// the same as the example in `docs/iam/access-manager-plugin.go` -
// specifically, it denies only `s3:Put*` operations on non-root accounts.
func (s *TestSuiteIAM) TestAccMgmtPlugin(c *check) {
	ctx, cancel := context.WithTimeout(context.Background(), testDefaultTimeout)

    protected FessConfig fessConfig;

    /**
     * Default constructor.
     */
    public LdapManager() {
        // do nothing
    }

    /**
     * Initializes the LDAP manager.
     */
    @PostConstruct
    public void init() {
        if (logger.isDebugEnabled()) {
            logger.debug("Initializing {}", this.getClass().getSimpleName());
        }

////

Buradaki tek yeni seçenek `--workers`; bu seçenek Uvicorn'a 4 adet worker process başlatmasını söyler.

Ayrıca her process'in PID'inin gösterildiğini de görebilirsiniz: parent process için `27365` (bu process manager), her worker process için de bir PID: `27368`, `27369`, `27370` ve `27367`.

## Deployment Kavramları { #deployment-concepts }

            Map<String, String> sysprops = Map.of(
                "java.awt.headless",
                "true",
                "tests.artifact",
                project.getName(),
                "tests.security.manager",
                "true",
                "jna.nosys",
                "true"
            );
            test.systemProperties(sysprops);

analytics and application data workloads. For more detailed documentation please visit [here](https://docs.minio.io/) ## Introduction This chart bootstraps MinIO Cluster on [Kubernetes](http://kubernetes.io) using the [Helm](https://helm.sh) package manager. ## Prerequisites - Helm cli with Kubernetes cluster configured. - PV provisioner support in the underlying infrastructure. (We recommend using <https://github.com/minio/direct-csi>) - Use Kubernetes version v1.19 and later for best experience. ##...

application data workloads. For more detailed documentation please visit [here](https://min.io/docs/minio/linux/index.html) ## Introduction This chart bootstraps MinIO Cluster on [Kubernetes](http://kubernetes.io) using the [Helm](https://helm.sh) package manager. ## Prerequisites - Helm cli with Kubernetes cluster configured. - PV provisioner support in the underlying infrastructure. (We recommend using <https://github.com/minio/direct-csi>) - Use Kubernetes version v1.19 and later for best experience. ##...

application data workloads. For more detailed documentation please visit [here](https://min.io/docs/minio/linux/index.html) ## Introduction This chart bootstraps MinIO Cluster on [Kubernetes](http://kubernetes.io) using the [Helm](https://helm.sh) package manager. ## Prerequisites - Helm cli with Kubernetes cluster configured. - PV provisioner support in the underlying infrastructure. (We recommend using <https://github.com/minio/direct-csi>) - Use Kubernetes version v1.19 and later for best experience. ##...

application data workloads. For more detailed documentation please visit [here](https://min.io/docs/minio/linux/index.html) ## Introduction This chart bootstraps MinIO Cluster on [Kubernetes](http://kubernetes.io) using the [Helm](https://helm.sh) package manager. ## Prerequisites - Helm cli with Kubernetes cluster configured. - PV provisioner support in the underlying infrastructure. (We recommend using <https://github.com/minio/direct-csi>) - Use Kubernetes version v1.19 and later for best experience. ##...