Livio Spring a0c3ccecf7 fix: use a single translator for middleware (#10633) ...

# Which Problems Are Solved

Comparing the v3 and v4 deployments we noticed an increase in memory
usage. A first analysis revealed that it might be related to the
(multiple) initialization of the `i18n.Translator`, partially related

# How the Problems Are Solved

Initialize the tranlator once (apart from the translator interceptor,
which uses context / request specific information) and pass it to all
necessary middleware.

# Additional Changes

Removed unnecessary error return parameter from the translator
initialization.

# Additional Context

- noticed internally
- backport to v4.x

2025-09-09 06:34:59 +00:00

..

connect_middleware

fix: use a single translator for middleware (#10633)

2025-09-09 06:34:59 +00:00

middleware

fix: use a single translator for middleware (#10633)

2025-09-09 06:34:59 +00:00

gateway.go

feat: exchange gRPC server implementation to connectRPC (#10145)

2025-07-04 14:06:20 +00:00

probes_test.go

refactor: rename package errors to zerrors (#7039)

2023-12-08 15:30:55 +01:00

probes.go

refactor: rename package errors to zerrors (#7039)

2023-12-08 15:30:55 +01:00

server.go

fix: use a single translator for middleware (#10633)

2025-09-09 06:34:59 +00:00