lukaszraczylo a774f9905b fix(logging): make level and field-name access concurrency-safe ...

SetFieldName wrote a package-global map with no lock while log read it
from many goroutines, and the level, caller, and time-format setters
mutated fields without synchronisation. A runtime setter call could
crash the process with a concurrent map write.

The scalar fields now use atomics on the hot log path and the global
field-name map uses a read-write mutex. Behaviour for init-time
configuration is unchanged.

2026-08-14 11:10:01 +01:00

..

logger_additional_test.go

Gofmt the codebase.

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

logger_bench_test.go

fixup! Gofmt the codebase.

2025-02-26 01:03:44 +00:00

logger_race_test.go

fix(logging): make level and field-name access concurrency-safe

2026-08-14 11:10:01 +01:00

logger_suite_test.go

Update cache library, use miniredis for testing, add additional benchmarks. (#14)

2024-06-19 23:10:36 +01:00

logger_test.go

fix(logging): make level and field-name access concurrency-safe

2026-08-14 11:10:01 +01:00

logger.go

fix(logging): make level and field-name access concurrency-safe

2026-08-14 11:10:01 +01:00