zeekayandHanzo Dev d047dc7311 notifier: answer an unset logger where the loop starts, not where it logs ...

forwardNotification logs on its first statement and runs on the goroutine Start
spawns, so a NotificationForwarder holding no logger dies there — and a panic on
that goroutine takes the process with it, since nothing above it can recover.

The logger can go unset two ways: NewNotificationForwarder stores whatever it is
handed, and Log is exported, so a struct literal can simply omit it. Start is the
one place the loop begins and the only route to run(), so answering it there
covers both ways at once, which defaulting in the constructor alone would not.

This is the same answer bootstrap.New, summary.New and the engine's NewWithConfig
already give; the forwarder was the remaining exported constructor without it.

Co-authored-by: Hanzo Dev <[email protected]>

2026-09-01 22:40:08 -07:00

..

handler

notifier: answer an unset logger where the loop starts, not where it logs

2026-09-01 22:40:08 -07:00

sender

refactor: update dependencies and engine improvements

2026-01-05 01:28:53 -08:00

timeout

refactor: update dependencies and engine improvements

2026-01-05 01:28:53 -08:00

tracker

Update context interfaces and quasar witness

2025-12-13 09:52:26 +00:00