mirror of
https://codeberg.org/forgejo/forgejo.git
synced 2025-08-19 17:01:12 +00:00
a9d09e5019
- It was possible for Forgejo adminstrators to configure the logger to log the goroutine PID that made the `Log` call.
- The need for the goroutine PID to be logged is that it might give insight which request or otherwise process made the log call by correlating the PID with other logs. However even for a single request I cannot make correlations between the goroutine PIDs and it seems that this particular need cannot be fulfilled by the current implementation.
- The gathering of this PID is discouraged, https://go.dev/doc/faq#no_goroutine_id, and the current implementation is a hack and can break in future Go releases; it has broken before in
|
||
|---|---|---|
| .. | ||
| color.go | ||
| color_console.go | ||
| color_console_other.go | ||
| color_router.go | ||
| event_format.go | ||
| event_format_test.go | ||
| event_writer.go | ||
| event_writer_base.go | ||
| event_writer_buffer.go | ||
| event_writer_buffer_test.go | ||
| event_writer_conn.go | ||
| event_writer_conn_test.go | ||
| event_writer_console.go | ||
| event_writer_file.go | ||
| flags.go | ||
| flags_test.go | ||
| init.go | ||
| level.go | ||
| level_test.go | ||
| logger.go | ||
| logger_global.go | ||
| logger_impl.go | ||
| logger_impl_test.go | ||
| logger_test.go | ||
| manager.go | ||
| manager_test.go | ||
| misc.go | ||
| stack.go | ||