lukaszraczylo 7e0d1e19b1 fix(circuitbreaker): guard nil monitoring to prevent boot panic ...

Starting with ENABLE_CIRCUIT_BREAKER=true panicked at boot: parseConfig -> initCircuitBreaker registers a metrics gauge, but cfg.Monitoring is assigned later by StartMonitoringServer, so the registration dereferenced a nil *MetricsSetup.

Add nil-receiver guards to the MetricsSetup registration methods (RegisterMetricsGauge/GaugeFunc/Counter, RegisterFloatCounter, RegisterMetricsSummary/Histogram), matching their existing 'return a dummy to prevent panics' contract. The guard is a no-op for non-nil receivers, so existing callers are unaffected. The breaker and the admin dashboard (which reads gobreaker state directly) keep working.

Add regression tests for the nil-receiver methods and for initCircuitBreaker with nil monitoring.

2026-06-21 02:48:37 +01:00

..

defaults.go

Add LRU cache support.

2025-12-03 10:22:33 +00:00

helpers_bench_test.go

improvements mid may 2025 (#24)

2025-09-30 18:27:33 +01:00

helpers_test.go

fixup! Disable caller as it's not necessary and generates slight delay.

2024-06-20 08:41:33 +01:00

helpers.go

Fix nil pointers + improve the cleanup.

2025-11-11 10:43:07 +00:00

monitoring_additional_test.go

Gofmt the codebase.

2025-02-26 00:47:41 +00:00

monitoring_test.go

Gofmt the codebase.

2025-02-26 00:47:41 +00:00

monitoring.go

fix(circuitbreaker): guard nil monitoring to prevent boot panic

2026-06-21 02:48:37 +01:00

nil_safety_test.go

fix(circuitbreaker): guard nil monitoring to prevent boot panic

2026-06-21 02:48:37 +01:00

structs.go

improvements mid may 2025 (#24)

2025-09-30 18:27:33 +01:00