Stephan Renatus bc8e23a174 logging: keep forwarding from BufferedLogger after Flush() (#8544) ...

The BufferedLogger introduced for logger plugins is created at startup
and passed to the `*plugins.Manager`. Plugins (bundle, discovery,
status, logs) cache `manager.Logger()` in a field at construction time.
After `Manager.Start()`, `ResolveBufferedLogger` flushes the buffer and
swaps the `Manager'`s logger to a `StandardLogger` — but the plugins
still hold the old `BufferedLogger`. Since bundle loading is async, the
"Bundle loaded and activated successfully" message (and similar) gets
written to the already-flushed buffer where nobody reads it.

Signed-off-by: Stephan Renatus <stephan.renatus@gmail.com>

2026-04-22 07:42:51 +00:00

..

test

logging: make WithContext() optional

2026-03-30 10:20:13 +02:00

buffered_logger_test.go

logging: keep forwarding from BufferedLogger after Flush() (#8544)

2026-04-22 07:42:51 +00:00

buffered_logger.go

logging: keep forwarding from BufferedLogger after Flush() (#8544)

2026-04-22 07:42:51 +00:00

logging_test.go

build: bump Go version requirement to 1.24 (#7839)

2025-08-24 09:02:09 +02:00

logging.go

logging: make WithContext() optional

2026-03-30 10:20:13 +02:00