v0.20.1
Patch release for the v0.20.x client latency-breaker configuration path.
Fixes
- Validate latency-breaker configuration during
Serviceinitialization:- thresholds and rolling window must be non-negative
- recovery count must be non-negative
- pass-through fraction must be in
[0, 1]
- Normalize latency-breaker defaults in one path so direct
client.Configusage andWithLatencyBreaker(...)behave consistently:- rolling window defaults to
1s - recovery count defaults to
3 - pass-through fraction defaults to
0.01
- rolling window defaults to
- Wrap
Service.init()errors with contextual%werrors while preserving the original cause.
Migration
No migration required for existing callers. The latency breaker remains disabled unless at least one latency threshold is configured.