ginuerzh 8d253dcd88 fix(logger): rotate a file log that names no rotation ...

A log config can name an output without naming a rotation, and that
combination used to receive a plain *os.File — nothing rotates it, ever.
One spoke on Android ran debug-level logging into exactly that shape and
grew the file to 111MB with no backups, which on a phone is not untidy so
much as fatal.

Default the rotation instead. The values match what an unconfigured
logger has always carried, so naming an output is no longer a way to ask
for an unbounded file, and a configured rotation still wins as written.
outputWriter is split out of ParseLogger so the decision — the part that
chooses whether a file log stops growing — is testable without a logger.

Signed-off-by: Step 5 Preview Free <noreply@stepfun.com>

2026-10-13 02:40:19 +00:00

..

cmd

fix(cmd): restore unix socket port-forward semantics

2026-08-17 22:51:00 +08:00

loader

feat: Global nodes registry for reusing nodes across hops

2026-10-02 22:23:34 +08:00

parsing

fix(logger): rotate a file log that names no rotation

2026-10-13 02:40:19 +00:00

config.go

feat: Global nodes registry for reusing nodes across hops

2026-10-02 22:23:34 +08:00