RamonandMax Peintner fca2589fc3 fix(login): http 2 memory leak's (#11830) ...

# Which Problems Are Solved
All http 2 based connect-es clients caused memory leaks in our testing
using the login v2 application as the host.

# How the Problems Are Solved
Switch to connect-rpc based http 1.1 transport for the login v2

# Additional Changes
Improved the otel interceptor implementation and tests.

# Additional Context
- connect-rpc is only enabled for v2 API's so we have to make sure to
not use any v1 apis in the login but this should be the case anyways.
- Discussion #10562

---------

Co-authored-by: Max Peintner <max@caos.ch>

2026-03-17 14:29:21 +00:00

..

.env.db

chore: rehaul DevX (#10571)

2025-10-08 10:27:02 +02:00

compose.sh

chore: rehaul DevX (#10571)

2025-10-08 10:27:02 +02:00

devcontainer.json

chore(build): enhance proto caching and install binary plugins for improved performance, remove reliance on BSR (#11634)

2026-02-19 08:04:17 +00:00

docker-compose.yaml

fix(login): http 2 memory leak's (#11830)

2026-03-17 14:29:21 +00:00

project.json

fix: improve NX caching (#11434)

2026-01-29 14:42:52 +01:00