wxiaoguang 674df05b16 Use stderr as fallback if the log file can't be opened (#26074) ... If the log file can't be opened, what should it do? panic/exit? ignore logs? fallback to stderr? It seems that "fallback to stderr" is slightly better than others ....		2023-07-24 04:57:21 +00:00
..
color.go
color_console.go
color_console_other.go
color_console_windows.go
color_router.go
event_format.go
event_format_test.go
event_writer.go
event_writer_base.go	Improve logger Pause handling (#24946)	2023-05-27 22:35:44 +02:00
event_writer_conn.go
event_writer_conn_test.go	Improve queue and logger context (#24924)	2023-05-26 07:31:55 +00:00
event_writer_console.go
event_writer_file.go	Use stderr as fallback if the log file can't be opened (#26074)	2023-07-24 04:57:21 +00:00
flags.go
flags_test.go
groutinelabel.go
groutinelabel_test.go
init.go	Do not output "Trace" level logs from process manager by default (#24952)	2023-05-27 10:55:24 +00:00
level.go
level_test.go
logger.go
logger_global.go	Fix sub-command log level (#25537)	2023-06-28 08:02:06 +02:00
logger_impl.go	Fix sub-command log level (#25537)	2023-06-28 08:02:06 +02:00
logger_test.go	Improve queue and logger context (#24924)	2023-05-26 07:31:55 +00:00
manager.go	Do not output "Trace" level logs from process manager by default (#24952)	2023-05-27 10:55:24 +00:00
manager_test.go	Fix sub-command log level (#25537)	2023-06-28 08:02:06 +02:00
misc.go
stack.go