"mypy >=1.14.1",
    "pwdlib[argon2] >=0.2.1",
    "pyjwt >=2.9.0",
    "pytest >=9.0.0",
    "pytest-codspeed >=4.2.0",
    "pyyaml >=5.3.1,<7.0.0",
    "sqlmodel >=0.0.31",
    "strawberry-graphql >=0.200.0,<1.0.0",
    "ty>=0.0.9",
    "types-orjson >=3.6.2",
    "types-ujson >=5.10.0.20240515",
    "a2wsgi >=1.9.0,<=2.0.0",
    "pytest-xdist[psutil]>=2.5.0",
    "pytest-cov>=4.0.0",

Çünkü uygulamamız proxy arkasında `/api/v1` path prefix'i ile çalışmaktadır; frontend'in OpenAPI şemasını `/api/v1/openapi.json` üzerinden çekmesi gerekir.

```mermaid
graph LR

browser("Browser")
proxy["Proxy on http://0.0.0.0:9999/api/v1/app"]
server["Server on http://127.0.0.1:8000/app"]

browser --> proxy
proxy --> server
```

/// tip | İpucu

   * Finalizer directly with no problems.
   *
   * If this library is loaded in an application class loader, it's important that Finalizer not
   * have a strong reference back to the class loader. Otherwise, you could have a graph like this:
   *
   * Finalizer Thread runs instance of -> Finalizer.class loaded by -> Application class loader
   * which loaded -> ReferenceMap.class which has a static -> FinalizableReferenceQueue instance
   *

import com.google.common.base.Predicate;
import com.google.common.base.Splitter;
import com.google.common.collect.ImmutableList;
import com.google.common.collect.ImmutableSet;
import com.google.common.graph.SuccessorsFunction;
import com.google.common.graph.Traverser;
import com.google.common.hash.HashCode;
import com.google.common.hash.HashFunction;
import com.google.errorprone.annotations.CanIgnoreReturnValue;

- Integrate with `CIFSContext` for witness support
- Modify `SmbTransport` for failover handling
- Update `DfsResolver` for witness-aware resolution

---

## Implementation Dependencies

```mermaid
graph TD
    A[SMB3 Leases] --> B[Directory Leasing]
    A --> C[Persistent Handles]
    C --> D[Multi-Channel]
    D --> E[RDMA Support]
    C --> F[Witness Protocol]
    D --> F
```

## Testing Strategy

* Selbst Abhängigkeiten können Abhängigkeiten haben, woraus eine Hierarchie oder ein **„Graph“ von Abhängigkeiten** entsteht.
* Alles **automatisch gehandhabt** durch das Framework.

	quarkus/extensions/vertx-http/runtime/pom.xml
quarkus/extensions/vertx-graphql/deployment/pom.xml
	quarkus/extensions/vertx-http/deployment/pom.xml
	quarkus/core/deployment/pom.xml
	quarkus/extensions/vertx-graphql/runtime/pom.xml
	quarkus/test-framework/junit5-internal/pom.xml
quarkus/extensions/smallrye-graphql-client/runtime/pom.xml
	quarkus/core/runtime/pom.xml
	quarkus/extensions/arc/runtime/pom.xml

Parce que nous avons un proxy avec un préfixe de chemin `/api/v1` pour notre application, le frontend doit récupérer le schéma OpenAPI à `/api/v1/openapi.json`.

```mermaid
graph LR

browser("Browser")
proxy["Proxy on http://0.0.0.0:9999/api/v1/app"]
server["Server on http://127.0.0.1:8000/app"]

browser --> proxy
proxy --> server
```

/// tip | Astuce

Como temos um proxy com um prefixo de path de `/api/v1` para nossa aplicação, o frontend precisa buscar o OpenAPI schema em `/api/v1/openapi.json`.

```mermaid
graph LR

browser("Browser")
proxy["Proxy on http://0.0.0.0:9999/api/v1/app"]
server["Server on http://127.0.0.1:8000/app"]

browser --> proxy
proxy --> server
```

/// tip | Dica

* Even dependencies can have dependencies, creating a hierarchy or **"graph" of dependencies**.
* All **automatically handled** by the framework.
* All the dependencies can require data from requests and **augment the path operation** constraints and automatic documentation.